MediaMonkey forum

MediaMonkey have several threads taking up 35 000 kB each. In addition, almost every time I quit the program, the process doesn't quit.

Tested in Windows Vista.

it happens often to me too that the mm process doesn't end when I quit MM.

I have had this problem with almost all the debug versions of mm3. So I wonder if this is not related with the debug.

(I'm on xp sp2)

This is happening to me also. I'm running 3.0.3.1140 debug version.

There seems to be no rhyme nor reason to when it exhibits this behavior, but seems to happen mostly if I have been editing a lot of tracks and then run the "Maintain Library" File Menu option.

nethog wrote:This is happening to me also. I'm running 3.0.3.1140 debug version.

There seems to be no rhyme nor reason to when it exhibits this behavior, but seems to happen mostly if I have been editing a lot of tracks and then run the "Maintain Library" File Menu option.

Happens to me, too. But Only when I load my scripts. I did not take the time to find out which one is the resource killer.

OK, seems to be when I've made changes to tags and after the status bar shows that the tags have been written, I close MM. While the status bar shows that MM is done writing the tags the database still has the journal open when I close.

The interface closes but the process doesn't, apparently because it hasn't finished updating the database. However, watching the open process and the temporary journal file for some time, it never does finish updating the database, close the journal and terminate the process.

After waiting 15 minutes, I killed the process the temporary journal file disappears. Reopening MM shows that my changes did not get written to the database.

Hope that made sense.

The last time it happened to me, I know it was the debug version, but I'm not sure if I've only seen it in the debug version. I haven't got any custom scripts--just the default installation. The most recent time it happened, I had started MM, updated podcasts, and maybe sych'd my iPod Shuffle.

Morten wrote:MediaMonkey have several threads taking up 35 000 kB each. In addition, almost every time I quit the program, the process doesn't quit.

Related?:
http://www.mediamonkey.com/forum/viewto ... 896#133896

Macarena wrote:

Morten wrote:MediaMonkey have several threads taking up 35 000 kB each. In addition, almost every time I quit the program, the process doesn't quit.

Related?:
http://www.mediamonkey.com/forum/viewto ... 896#133896

Yes.

If you are experiencing this problem, could you please generate a debug log? I also wonder, whether removing d_iPhone.dll plug-in from MM fixes the issue (just a guess, since it's a new plug-in).

Jiri

jiri wrote:If you are experiencing this problem, could you please generate a debug log? I also wonder, whether removing d_iPhone.dll plug-in from MM fixes the issue (just a guess, since it's a new plug-in).

Jiri

Sure, just tell me how do you generate one after the program has closed?

/signed

I get this a lot, but specifically ONLY when for some reason a process that is running as a background thread hangs. It seems to prevent the main MM from then properly closing itself. So when you try to start up MM again, you get "clones" - which generally don't load up past the splash screen, but it looks like for some of you, it does.

I posted about this on the bug forum, with volume levelling - http://www.mediamonkey.com/forum/viewtopic.php?t=26625 - but I've since seen it when cd-burning hangs too.

There are also indications that the background process still is continuing to work, it's the UI that gets stuck (ie, when my cd burns "stop" at track 2 or 3, the cd is actually finished, but I have to reboot to get MM and the burner to both reset).

I have other users confirming that this problem exists.

i had the same problem until i uninstalled tweakmonkey... everything seems fine now.

I also have this issue,

Running Vista with latest Beta (3.0.3)

I'm having a great of trouble trying to exit out of MM3 with this latest version (3.0.3.1140). Not sure what it is, but I do know it's happening on two separate computer, one on vista one on xp, and neither with any plug-ins.