by davidbspalding » Sun Jul 08, 2012 3:05 pm
Environment: Win XP Pro SP3, bulk of music library on NAS share, podcasts locally stored, temporary music library locally stored.
MM version 4.0.6.1501
Immediately upon updating to 4.0.6, I noticed MM running very very slowly. Systinternals Process Explorer indicates its maxing out the CPU at or above 93%.
I've run the debug version, and recorded three files. With DLNA sharing enabled, MM 4.0.6 seems unable to close the process entirely, and has to be killed. The final log (without kernel tracking) includes MM 4.0.6 being run, closed, then run again (the prior process had to be killed, then DLNA being deselected, and closing (process closed itself normally.
I've left MM 4.0.6 alone for 5-10 minutes at a time at runtime, and the CPU behavior doesn't seem to abate for at least 10-15 mins or longer, just keeps chugging away (as illustrated):
http://chromejob.com/mediamonkey/201207 ... pu_hog.png
Net result of this is that nothing else can be performed on the computer while this is occurring.
Log files attached to the support ticket, and available here: chromejob.com/mediamonkey/20120708_gqn-249754_mediamonkey_dbug_logs.zip
Environment: Win XP Pro SP3, bulk of music library on NAS share, podcasts locally stored, temporary music library locally stored.
MM version 4.0.6.1501
Immediately upon updating to 4.0.6, I noticed MM running very very slowly. Systinternals Process Explorer indicates its maxing out the CPU at or above 93%.
I've run the debug version, and recorded three files. With DLNA sharing enabled, MM 4.0.6 seems unable to close the process entirely, and has to be killed. The final log (without kernel tracking) includes MM 4.0.6 being run, closed, then run again (the prior process had to be killed, then DLNA being deselected, and closing (process closed itself normally.
I've left MM 4.0.6 alone for 5-10 minutes at a time at runtime, and the CPU behavior doesn't seem to abate for at least 10-15 mins or longer, just keeps chugging away (as illustrated):
http://chromejob.com/mediamonkey/20120708c_mediamonkey_cpu_hog.png
Net result of this is that nothing else can be performed on the computer while this is occurring.
Log files attached to the support ticket, and available here: chromejob.com/mediamonkey/20120708_gqn-249754_mediamonkey_dbug_logs.zip