View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0021232 | MMW 5 | Main Panel: Toolbars & Menus | public | 2024-09-25 21:53 | 2024-09-27 20:34 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.1 | ||||
| Target Version | 5.1 | Fixed in Version | 5.1 | ||
| Summary | 0021232: Menus sometimes fail to respond and trigger 100% CPU utilization | ||||
| Description | MM menu's often fail to display, until the context menu is used. 0 Open MM in Music [Grid] 1 Click a main menu entry --> the menu displays 2 Move the cursor over other main menu entries --> Sometimes they'll open, and sometimes they won't! 3 Once a menu has opened, e.g. View, click View again to close it, and then click another menu (e.g. Edit) to open it and immediately hover the mouse over another menu --> It'll take several seconds for the menu to open! 4 Right click on an album in the grid --> Context menu opens 5 Repeat steps 1-3 on the main menus --> Now the menus function correctly Note: this is annoying but not that severe. I've tagged it as 'urgent' because it occasionally (rarely) causes CPU utilization to go to 100% When the CPU jumps to 100%, crashlog CF5D0000 was sent. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3059 | ||||
|
|
Further testing reveals that this occurs even with the network disabled and with dbgview not running (in fact the 100% CPU utilization problem is more likely to occur when dbgview isn't running: Crashlog ID A14A07AE Task Queue Deadlock Sharing a video/debuglog offline. |
|
|
Interestingly, this doesn't occur on a clean install of MMW 5.1, implying that it's related to Devices, Podcasts, Library sharing, cdplayer.ini, a more complex database (that has gone through several upgrades over time) OR something similar that has been configured in my original installation but not in the clean installation. Hopefully the debug log shows the culprit. |
|
|
Fixed in build 3059. It was combination of more things, the key to reproduce was active shuffle, last focus on collection node and not very small DB. |
|
|
Verified 3059. |
