For me, after I renamed d_iPhone.dll then MediaMonkey exits completely consistently. I can then nl longer replicate this problem. Before renaming d_iPhone.dll I could, perhaps not 100% of the time, but very often.

Same problem here, build 1232 on XP. I just have a really hard time reproducing it in any consistent way. I dont have any portables plugged in when it happens.

When it happens, I can launch MM again and then have two processes of mediamonkey.exe running, even though I have the option set to only allow one instance.

Maybe its to do with the last.fm plugin - or maybe its from closing with alt+F4 - like I said hard to reproduce since it doesn't happen every launch of MM.

I'm also experiencing the same issue, renaming d_iPhone.dll resolves it. MM would crash at shutdown, which also removed the contents of the 'now playing' node.

[quote="Starbuck"]I tried replicating this when closing mediamonkey today. Task manager shows mediamonkey still running in memory.[/quote]
Seems to be the same behavior I reported in [url]http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=38343[/url]

Guy

The existence of d_iPhone.dll also causes MM to eat cpu cycles on my system. I have reported both issues but am not sure if it is being looked into.

Something changed with d_iPhone.dll going from 3.0 to 3.1 - in 3.0 MM hung on startup if one didn't rename d_iPhone.dll. In 3.1 MM does start up but doesn't exit correctly and also needlessly eats cpu cycles (perhaps there is some polling going on in a loop internally?).

I don't think I have quicktime software anymore either, but am not 100% sure since I don't know the proper way to check for the existence of it.

Nice, this seems to do the trick.

And indeed, I do not have any apple software installed on my computer. Think this is a **** ** *** *** on Windows. I use VLC for all kinds of video playback :)

Mist, when I rename d_iPhone.dll then MediaMonkey exits completely (see [url]http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=38544[/url]). Have you tried that?

Nope, this has nothing to do with it I guess. Just because of the simple fact there are no devices connected in any way...

I guess that's related to this: http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=8&nav=0,1

[3728] WMDM: Closing WMDM
[3728] WMDM: Queueing action id:0
[3728] WMDM: Waiting for queued actions to terminate
...
[3728] WMDM: Waiting for queued actions to terminate
[3728] MMDS: Smooth stopping for some time, stop now
[3728] MMDS: Buffer.Close() starting.
[3728] MMDS: Buffer.Close() finished.
[3728] MMDS: Stopped
[3728] WMDM: Waiting for queued actions to terminate
[3728] WMDM: Waiting for queued actions to terminate
[3728] WMDM: Waiting for queued actions to terminate
[3728] WMDM: Waiting for queued actions to terminate
...

I have captured a logg on shutdown. Buffers shuts down perfectly, WMDM not.

[code]
[3728] WMDM: Closing WMDM
[3728] WMDM: Queueing action id:0
[3728] WMDM: Waiting for queued actions to terminate
...
[3728] WMDM: Waiting for queued actions to terminate
[3728] MMDS: Smooth stopping for some time, stop now
[3728] MMDS: Buffer.Close() starting.
[3728] MMDS: Buffer.Close() finished.
[3728] MMDS: Stopped
[3728] WMDM: Waiting for queued actions to terminate
[3728] WMDM: Waiting for queued actions to terminate
[3728] WMDM: Waiting for queued actions to terminate
[3728] WMDM: Waiting for queued actions to terminate
...
[/code]

And it goes on like this until you stop MediaMonkey.exe manually from the task manager.

I downloaded and installed 3.1.0.1229 and this happens on my machine (Vista) as well - not all the time but quite frequently.

When you exit MediaMonkey the toplevel window goes away and you think it has exited. But, Windows Task Manager reveals that MediaMonkey.exe is hanging around. Again, it doesn't happen at every invocation of MediaMonkey but quite often.

I tried to get a log but whenever I run DbgView, then MediaMonkey exits fully and completely. I also tried attaching a regular debugger to an already running MEdiaMonkey, but again whenever I do that MediaMonkey exits fully and completely, so I can not obtain a log.

[quote="DaKo"]Unfortunately MediaMonkey is closed by Windows so there isn't an option to create a debug log. Is there any other way to create one when MediaMonkey crashes?[/quote]
Please read the linked post, it describes exactly how to obtain the log:

[quote]For functional problems (i.e. no crash or error) or if you can't generate a debug log as described above, you can manually generate a debug log as described below:
- Install a debug version of MediaMonkey (if necessary) on top of the current beta. Debug versions of MediaMonkey are usually posted within each Alpha/Beta/RC announcement. Make certain that the debug version# matches the beta version#. Note that Alpha builds are always debug builds (i.e. no special download is required.
- Download the DbgView application from: http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx
- Execute DbgView.
- If you know that the bug triggers a system freeze, configure DbgView to save the log to a file automatically via File > Log to File...
- Execute MediaMonkey_Debug.exe and try to reproduce the bug with a small set of Tracks.
- You'll see logs being generated in DbgView. Save the log messages from DbgView to a file if necessary.[/quote]

Unfortunately MediaMonkey is closed by Windows so there isn't an option to create a debug log. Is there any other way to create one when MediaMonkey crashes?

Please create a debug log as per above.

MediaMonkey crashes in Vista when I want to close it manually (Vista says that there's an error with MediaMonkey). But this occurs irregularly ... It seems to be odd because the builds before 1227 (or maybe before 1225) worked like a charm. No new plugins were installed. Could this be a related issue?