View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0014490 | MMW v4 | Other | public | 2017-10-25 19:24 | 2018-04-03 11:43 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Target Version | 4.1.19 | Fixed in Version | 4.1.19 | ||
| Summary | 0014490: CPU utilization at 50% | ||||
| Description | I've twice observed a strange CPU utilization problem: when I leave MMW 4.1.18.1853+ running for a long time (I left it open at Music > Location > D: > Documents > Temp > Jagged little pill), it gets into a state in which it becomes very slow to respond to UI interaction and CPU utilization stays at 50%. For example, just selecting a track can take several seconds. What's really strange is that even after closing and restarting MM (and verifying in Process Explorer that it shut down correctly), the problem remains! The only way to get rid of the issue is to restart the machine. Also interestingly, once the problem occurs, if I install 4.1.17, the problem occurs with that build. In other words, something in the machine's state seems to trigger the problem. Could it be related to the Windows Anniversary Update? Attached are debug logs of this occurring on 4.1.19, 4.1.18, and 4.1.17 (note: it occurred with 4.1.19 and then I tried 4.1.18/17 (without rebooting). | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 1859 | ||||
| related to | 0008291 | closed | jiri | MMW v4 | Faster image resizing |
| related to | 0006467 | closed | Ludek | MMW v4 | Error loading Album art properties when there lots of high res images |
| related to | 0013926 | closed | Ludek | MMW v4 | Large Font slows Lyrics display in Art & Details window |
| related to | 0014527 | closed | michal | MMW 5 | Album Art tagging UI blocks other functionality |
| related to | 0014596 | closed | petr | MMW v4 | High CPU utilization during playback (regression) |
| related to | 0014564 | closed | michal | MMW 5 | Visualization Performance issues |
|
|
The only strange thing in the logs is that the first UpdateDriveLetters thread takes more than 30 seconds. Is the high CPU utilization only for 30 seconds after app start or longer? It would be good to try: a) disconnect all external drives, portable devices and medium (CD/DVD/BD) b) try to disable device plugins one by one (d_WMDM.dll, iPod.dll, iPhone.dll) c) try to disable UPnP.dll by disabling I mean to rename .dll => .dll.off If b) or c) helps then try to locate which plugin is causing it. If it isn't going to help then we should add more debug messages to the UpdateDriveLetters thread to see why it takes 30 seconds after app start. Another idea is that sometimes I saw (e.g. after failed video playback) that some additional processes like MediaMonkeyVideoHelper.exe, MediaMonkeyCOM.exe, MediaMonkey64Helper.exe remains running (even if you killed MediaMonkey.exe) Are you sure that you killed them all before next run of MM? |
|
|
Although the UpdateDriveLetters thread was slow, I think it might be something else since subsequent to the launch, selecting a track caused CPU to jump to 50% and stay there. Also: - all drives were disconnected. the only devices that were connected are devices that always are (keyboard, mouse, scanner, etc.) - all child process of MM had been terminated - CD was not inserted - CPU utilization seemed to be high at launch (e.g. it took a long time just for MM to start), but then it went down. But as soon as I clicked a node or track, CPU would go back up to 50% and stay there until MM was terminated. That's why I don't think it's related to drive letters. I'm going to try to replicate again, but so far I've had no luck... |
|
|
BTW are you sure that it was MM process that taken 50% CPU? Based on your description/info it looks more that rather another (system?) processes have taken it? Thus also all the other apps/processes were slower because something was taking much of the system resources? |
|
|
I've been able to replicate. It's related to navigating within the Music/Location folders. Here's a video, where you can see that initially the UI is relatively responsive, but after navigating within those folders it gradually gets impossible to use: https://www.screencast.com/t/5SiHbuR3nP8w I've also uploaded the corresponding debug log. Strangely, on restarting MM the problem persists. |
|
|
As discussed offline, looks like artwork processing issue (related to 0008291 and 0006467) |
|
|
Update: It freezes in GDI32.dll | GetPixel when creating lyrics overlay. GDI32.dll | GetPixel is somehow very slow on Rusty's machine. i.e. there are two issues: 1) our TBitmap32.TextOut() needs optimizations, probably to use ScanLine() instead of GetPixel() ? Related to 0013926 2) Rusty has probably an issue with graphic card drivers on his machine |
|
|
TBitmap32.TextOut() optimized in 4.1.19.2059 and confirmed by Rusty that it solves the CPU utilization issue. |
|
|
Verified build 1859 |
