[quote="Ludek"]Just disable
Options -> Media Sharing -> <server> -> UPnP/DLNA server -> [x] Update Play Counter
this disables scrobbling too.[/quote]

Thank you for that! Very nice.

Stability has been excellent for the last few builds, Ludek. Thanks. I've fixed grunty bugs like that in the past and they're not much fun.

[quote="Undertone"]'ve been having this problem (trying to close MM, doesnt, then freezes) for about 3 months[/quote]You still see this on build 1626?

I've been having this problem (trying to close MM, doesnt, then freezes) for about 3 months (No addons or anything else added)..with all the bugs that MM has I didnt know where to start to explain it. I'm so glad somebody brought this up..Thx mcow..I always have to CTRL-ALT-DEL to close MM.


I have another issue that could be related. When I have tracks that are in a folder (a folder that mm doesnt scan) and I try playing them with MM, I click on them so that mm plays them. MM starts, does not play them and also freezes the folder where the tracks came from.

Are you also facing this mcow?

Just disable
Options -> Media Sharing -> <server> -> UPnP/DLNA server -> [x] Update Play Counter
this disables scrobbling too.

I've not had issues with MMW scrobbling local and UPnP playback simultaneously (except once where local plays were not scrobbled). As no clients scrobble I'm happy MMW scrobbles UPnP plays (however I've suggested this should be optional in the past (maybe the option to Update play counter can already disable scrobbling)).

So far, 1626 has been quite stable, no crashes.

I can suggest one possibility behind that scrobbler crash. I was playing from MMW to the stereo, and at the same time fooling around with MMA, and I inadvertantly started playing from UPnP. But MMW automatically scrobbles songs that it serves up via UPnP -- which I don't think is such a good idea anyway: the player should be scrobbling, not the server. What if some guest is playing via my UPnP server? I don't want his private listens going into my scrobble history.

Anyway, having two scrobbling sources simultaneously could have been why I had two separate crashes from the scrobbler DLL. Maybe they were in contention for some resource.

It looks like a problem in the Last.FM Scrobbler addon, do you use the newest version, could you try to re-unstall it?

Problem signature:
  Problem Event Name:	BEX
  Application Name:	MediaMonkey.exe
  Application Version:	4.1.0.1625
  Application Timestamp:	5127cb2e
  Fault Module Name:	gen_LastFMScrobbler.dll_unloaded
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	4dffc8b2
  Exception Offset:	088a6f85
  Exception Code:	c0000005
  Exception Data:	00000008
  OS Version:	6.1.7601.2.1.0.768.3
  Locale ID:	1033
  Additional Information 1:	fa66
  Additional Information 2:	fa6696398de2b9f98383d7a3bf5c3ea1
  Additional Information 3:	fa66
  Additional Information 4:	fa6696398de2b9f98383d7a3bf5c3ea1

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


Problem signature:
  Problem Event Name:	BEX
  Application Name:	MediaMonkey.exe
  Application Version:	4.1.0.1625
  Application Timestamp:	5127cb2e
  Fault Module Name:	gen_LastFMScrobbler.dll_unloaded
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	4dffc8b2
  Exception Offset:	088a6db9
  Exception Code:	c0000005
  Exception Data:	00000008
  OS Version:	6.1.7601.2.1.0.768.3
  Locale ID:	1033
  Additional Information 1:	f3f6
  Additional Information 2:	f3f6a1403802118ada460cd45530935b
  Additional Information 3:	72eb
  Additional Information 4:	72ebf455a7c50c258dc65105bbeeaddd

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Problem signature:
  Problem Event Name:	BEX
  Application Name:	MediaMonkey.exe
  Application Version:	4.1.0.1625
  Application Timestamp:	5127cb2e
  Fault Module Name:	gen_LastFMScrobbler.dll_unloaded
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	4dffc8b2
  Exception Offset:	088a6f85
  Exception Code:	c0000005
  Exception Data:	00000008
  OS Version:	6.1.7601.2.1.0.768.3
  Locale ID:	1033
  Additional Information 1:	fa66
  Additional Information 2:	fa6696398de2b9f98383d7a3bf5c3ea1
  Additional Information 3:	fa66
  Additional Information 4:	fa6696398de2b9f98383d7a3bf5c3ea1

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


Problem signature:
  Problem Event Name:	BEX
  Application Name:	MediaMonkey.exe
  Application Version:	4.1.0.1625
  Application Timestamp:	5127cb2e
  Fault Module Name:	gen_LastFMScrobbler.dll_unloaded
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	4dffc8b2
  Exception Offset:	088a6db9
  Exception Code:	c0000005
  Exception Data:	00000008
  OS Version:	6.1.7601.2.1.0.768.3
  Locale ID:	1033
  Additional Information 1:	f3f6
  Additional Information 2:	f3f6a1403802118ada460cd45530935b
  Additional Information 3:	72eb
  Additional Information 4:	72ebf455a7c50c258dc65105bbeeaddd

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

I had another instance of the double-crash at shutdown. No crash log generated, these are hard Windows errors; I did not have dbgview running at the time. But I did look at the "details" part of the Windows error box, and they contained the following.
First error:
[code]
Problem signature:
Problem Event Name: BEX
Application Name: MediaMonkey.exe
Application Version: 4.1.0.1625
Application Timestamp: 5127cb2e
Fault Module Name: gen_LastFMScrobbler.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4dffc8b2
Exception Offset: 088a6f85
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: fa66
Additional Information 2: fa6696398de2b9f98383d7a3bf5c3ea1
Additional Information 3: fa66
Additional Information 4: fa6696398de2b9f98383d7a3bf5c3ea1

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Problem signature:
Problem Event Name: BEX
Application Name: MediaMonkey.exe
Application Version: 4.1.0.1625
Application Timestamp: 5127cb2e
Fault Module Name: gen_LastFMScrobbler.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4dffc8b2
Exception Offset: 088a6db9
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: f3f6
Additional Information 2: f3f6a1403802118ada460cd45530935b
Additional Information 3: 72eb
Additional Information 4: 72ebf455a7c50c258dc65105bbeeaddd

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt[/code]

Second, almost identical except for the "additional information" lines:
[code]
Problem signature:
Problem Event Name: BEX
Application Name: MediaMonkey.exe
Application Version: 4.1.0.1625
Application Timestamp: 5127cb2e
Fault Module Name: gen_LastFMScrobbler.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4dffc8b2
Exception Offset: 088a6f85
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: fa66
Additional Information 2: fa6696398de2b9f98383d7a3bf5c3ea1
Additional Information 3: fa66
Additional Information 4: fa6696398de2b9f98383d7a3bf5c3ea1

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Problem signature:
Problem Event Name: BEX
Application Name: MediaMonkey.exe
Application Version: 4.1.0.1625
Application Timestamp: 5127cb2e
Fault Module Name: gen_LastFMScrobbler.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4dffc8b2
Exception Offset: 088a6db9
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: f3f6
Additional Information 2: f3f6a1403802118ada460cd45530935b
Additional Information 3: 72eb
Additional Information 4: 72ebf455a7c50c258dc65105bbeeaddd

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
[/code]

The only ongoing features I had running were scrobbling and AutoDJ; no other plugins. I had played tracks from MMW, then later some tracks from MMA via UPnP, then sync'd, then closed the program.

You can send it to support: http://www.mediamonkey.com/support/index.php?_m=tickets&_a=submit

[quote="Peke"]Reopen, If you can replicate constantly can you please add more details and make things easier to find.[/quote]
Where to put the crash log?

Reopen, If you can replicate constantly can you please add more details and make things easier to find.

[quote="Ludek"]I found a problem in code that is most probably reason of this issue, will be fixed in 1624: http://www.ventismedia.com/mantis/view.php?id=10464[/quote]
I think MMW has been more stable with this fix -- I'm running 1624.

I reported a crash [url=http://www.mediamonkey.com/forum/viewtopic.php?f=19&t=69400#p360513]here[/url] that I thought might have been related to the automation-object issue I'm having. Yesterday I saw what seemed to be that same crash again, but without having run my script, nor having played or browsed from UPnP. The symptom is, I close the program, and get two "MediaMonkey has closed" errors from Windows. I have a crash log from the first time I saw this (when my script was running).

Today I saw the following:
Started MMW, sync'd plays from MMA, played some local tracks on MMA, played some on MMA from UPnP; then switched to MMW. While playing, sync'd MMA again. Later I noticed that, starting around this sync, scrobbling stopped. I exited MMW; then restarted the program; then opened the last.fm log. Got a crash at this point, and discovered that the first run of MMW had not exited entirely, which led to the crash when I tried to open the log. Did not get a log file for this.

I did not run my script yesterday or today. Both days I was running scrobbler and the ScrobblerDJ. I'm turning off ScrobblerDJ for the time being.

So, there are still some stability problems at shutdown.

[quote="Ludek"]I have also reproduced something similar, I think it might be related to UPnP/DLNA closing.[/quote]

I saw the symptom of window closing but program not exiting again. This time, I had not served UPnP from MMW. I had sync'd to MMA once, and then just played music, using ScrobblerDJ to keep the tunes going.

I did also have my monitoring plugin running: It's a Python script that subscribes to events from the automation object, which is responsible for [url=http://www.mediamonkey.com/forum/viewtopic.php?f=19&t=69400]another issue[/url]. I need to debug this when I get some time. Altho the script indicated that it detected MM shutting down, Python did not terminate (which it should, and did with 4.07); neither did MM. Even after killing Python, MM continued for minutes before I killed it.

I found a problem in code that is most probably reason of this issue, will be fixed in 1624: http://www.ventismedia.com/mantis/view.php?id=10464

I have also reproduced something similar, I think it might be related to UPnP/DLNA closing. Added more debug messages to build 1624 so that I could see more then.
In my case the closing has taken long (half of minute?), not forewer.