Abraxxa,

Thanks for taking the time to figure this one out.

If you don't mind, could you send me a Private message with a link to the file (e.g. using mediafire).

Thanks.

-Rusty

I guess I just found out what causes it, in_ape.dll causes MM to crash so I've moved all my ape files from my music directory.
I've found the damaged file and can supply it to you for research how to improve in_ape.dll to not cause this again if you want.

I've just uninstalled iTunes and it still happens.
Can I debug what MM is doing?

Abraxxa,

So the problem is specific to the file monitor (and seems to have nothing to do with synchronization).

Does it occur when iTunes has been uninstalled?

-Rusty

This happens when just starting MM without the iPhone attached.
The CPU usage of one cpu core goes to <5% after the file monitoring on startup has finished, the other one is at >95% right after starting MM and stays there.
The red line (show kernel times on) is over 60%, so it might involve some kind of IO.
MM hangs on close too so I have to kill the process and the file monitoring settings aren't saved.

abraxxa,

I've tested this with different versions of iTunes on MM 3.2.2.1300 (no relevant changes from 1299), with file monitor enabled/disabled. I can't reproduce any playback/CPU problems for tracks on the hard drive, though I did notice that if I play tracks off of the connected device, CPU utilization tends to increase.

Is that the problem that you were referring to (high CPU when playing off the iPhone)?

If you're referring to high CPU for playback of tracks off your hard drive, does the problem persist when you disable the file monitor? What about background auto-organize or volume analysis? What if you uninstall/re-install iTunes?

-Rusty

The debug log is from version 3.2.2.1299, so yes.
This problem appeared with the iTunes 9.2 update.

Abraxxa,

Is this problem new to 3.2.2? Does it still occur with 3.2.2.1299?

Does it occur with 3.2.1?

-Rusty

I followed the debug instructions and after the monitoring of my music folder is completed only the following log lines are shown in debugview:

[4552] Thread has started 3128
[4552] Thread registered, going to initialize 3128
[4552] Thread initialized 3128
[4552] Going to make final callback 3128
[4552] Thread has finished 3128

Those log lines are all within the same second and repeat with a different thread id every 30 seconds.

Try to create a debug log as it will show what MediaMonkey is doing, like this it is impossible to tell. Do you have any addons installed?

No response from the MediaMonkey Team?
The high cpu load seems to stop after about 30 minutes but MM hangs on close every time.

3.2.2.1298 still has 50% cpu usage all the time, quite annoying!

Here MM 3.2.1.1297 has exactly 50% CPU usage with iTunes 9.2 installed too!

Odd that it's been out for 10 days and you're the only one to report this. I'm wondering if there's something specific to your system causing this to happen?

I just upgraded to v3.2.1.1297, and upon startup MM immediately proceeded to use 100% of my dual-core CPU. I wasn't playing music, or doing anything at all.
Deleting d_iPhone.dll (and d_Ipod.dll for good measure) once again, then restarting MM seems to have fixed the issue.

BTW, as soon as I plug my iPhone into the computer, MM crashes (even after I removed these dlls).

Now why can't they fix this once and for all?