CPU running at 100% after add/rescan

[70melbatoast]

Posted this previously in the Bug Reports forum (thread found here), but thought it might get better visibility here, so please don't flame me:

Happy holidays to all!
I too am having similar issues as Cowboy.
Running:
Windows XP SP3
MM 3.2.0.1294
2GB Ram
Library consists of about 24,000 tracks about 75% MP3 & 25% FLAC stored and accessed via external hard drive.

The problem seemed to start after upgrading to 3.2. MM 3.2 runs great when playing music, or even while monitoring my music folder (CPU at around 30-35% when monitoring at initial program startup). This is perfectly normal for my PC - its a bit old. Music playback consumes about 2-4%.

My issue has been with adding new music to the library, specifically FLAC (it appears that this does not happen with MP3's). I D/L a lot of lossless music, specifically live shows from trade friendly bands. I will temporarily store the newly D/L'd music in a separate folder until I can properly tag it. When ready to tag and add to library I go into "My Computer" via MM's Tree and find the folder. From there I tag all the files, then when ready I right click on the folder in the Tree and select the "Add/Rescan tracks to the library..." option. As soon as it completes the transfer (and it usually does successfully), the CPU is pegged at 100%, when I attempt to close MM, I get a dialog asking me if i want to terminate background processes. Answering Yes or No has no effect, MM is still running at 100%. I have to go into task manager and kill MM.

Note that the above issue happens after the startup monitor has completed or I have terminated it manually.

Any help is greatly appreciated. Thank you.

Chad

[rovingcowboy]

you know whats funny about all the errors over the last 6 months or so?
i never got more then 3 of them on the old dell tower. but when i put the mm 3.2 on that newly built jukebox with everything being a fresh clean install.

i seem to be getting all the errors every one else got.?? now strange as that sounds. it tells me monkey is keeping some code from the previous version it over writes? which there was none on my jukebox since i formated the hd. but rusty and jiri and the others are trying to find out what is going on. just taking time with all the christmas partys to go to and all the kid's school christmas play's and now getting the tree's up and stuffing ones self with diner. there does not seem like much time to do code work?

[70melbatoast]

Anybody have any solutions? Please see the first post. I am still experiencing this on a fresh install of XP and MM 3.2.0.1294 Gold (no plug-ins)
This has been an extremely frustrating issue to an otherwise excellent program.

[Lowlander]

Do you have auto analyze volume for unanalyzed tracks enabled?

[nohitter151]

Do you have "Automatically analyze volume of unanayzed tracks" or "Analyze tracks for duplicates" checked in the options?

[rovingcowboy]

no i unchecked that on the jukebox and i still get it jumping from 10% usage to 100% usage doing song changes and from 0 to 40 doing playing of the song.

so that must be what was doing it on my system.
of course i also use that priority static control program and run mediamonkey in real time. that can also have something to do with knocking the usage down.

[70melbatoast]

Do you have "Automatically analyze volume of unanayzed tracks" or "Analyze tracks for duplicates" checked in the options?

nohitter151/lowlander;

Thanks for the response. I have neither option checked in the options. In addition, I've left MM untouched for several hours to see if it "finishes" whatever it was doing and the CPU is still pegged at 95-100% with nothing else running.

*Update*
I just tried an add/rescan on a FLAC album and predictably, it did work - it copied and renamed the files to the correct location (had no problem with this before). I just realized that I have "Delete empty folders" checked in the options and curiously the original folder is still there and IS empty (but not deleted)...and...predictably I go to close MM and I get the "Terminate background processes?" dialog. The CPU is showing that MM is only eating between 20-45%, an improvement yes, but not ideal - not when it never did this before. Trying to delete the folder manually through "My Computer" results in "This folder is being used by another..." dialog. When I kill the MM process, I can then manually delete the folder.

*Update 2*
Problem solved? Turns out that unchecking "Delete empty folders" seems to fix this issue. Hooray! BUT if you try to manually delete the old folder while MM is running through "My Computer" will still result in a "This folder is being used by another..." dialog. Sounds like a temporary solution for me, but I think it needs to be investigated further. Thanks for everyone's help!

[davidbspalding]

*Update 2*
Problem solved? Turns out that unchecking "Delete empty folders" seems to fix this issue. Hooray! BUT if you try to manually delete the old folder while MM is running through "My Computer" will still result in a "This folder is being used by another..." dialog. Sounds like a temporary solution for me, but I think it needs to be investigated further. Thanks for everyone's help!

I've encountered this regularly. I rip CDs to MP3s on my W: partition, tag, add artwork, re-tag, diddle, create M3u playlists, and then finally move them to the final repository which MM scans on startup. I move them with AutoOrganize, with "delete empty folders" checked. MM asks if I want to move the playlist file before deleting, I click "Yes, sir," and about 40% of the time, get an error that the folder cannot be deleted.

In some extreme cases, I have been unable to delete the folders in Windows, even after rebooting(!). As far's I could tell, something was marking the folder (or a hidden component) read-only. A week ago, I had to boot in Safe Mode to delete folders.

Is is possible MM is leaving a handle open on the folder objects?