Hello,
There is a problem I've been having with MCv14 for some time now which is driving me nuts. I've found some information, which might resonate with the MC devs?
Sometimes after hibernation MC is using 100% of one of my 4 CPUs in my Laptop causing the fan to spin up to full noise. It continues until I kill MC, and restart it.
In process explorer (procexp.exe) I can see the thread (3724) that is creating all the activity.
...and in Visual Studio I can see the 3724 thread Priority is set to "Lowest". (It's the only thread with this priority.)
...and in the MC logs I found this:
0355589: 7024: Import: Finish: Updating view schemes
0355620: 7024: Import: Finish: Updating UI (bWorkPerformed = 0)
0355620: 7024: Import: Finish: Notify UI of finish
0355620: 7024: Import: Finish: Destroying
0355620: 7024: Import: CSynchronizeDatabase::UpdateWatchFolders: Start
0355620: 7024: Import: CSynchronizeDatabase::UpdateWatchFolders: Starting watch thread
0355620: 3724: Import: CWatchFoldersThread::Thread: Start0355620: 4468: Import: CWatchFoldersThread::Thread: Finish (331128 ms)
0355620: 3724: Import: CWatchFoldersThread::Thread: Watching folder '\\ramesses\music\'0355636: 7024: Import: CSynchronizeDatabase::UpdateWatchFolders: Finish (16 ms)
0361345: 7024: SDK: CMJCurPlaylistAutomation::CMJCurPlaylistAutomation: Global Count: 5
0361345: 7024: SDK: CMJPlaybackAutomation::CMJPlaybackAutomation: Global Count: 4
Is it possible that the CWatchFoldersThread is burning 100% CPU after hibernation/wake-up, if it is set to scan a UNC network drive?
I hope this makes sense to the MC devs, because I enjoy using MC enormously.
thanks,
m