View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018958 | MMW 5 | General | public | 2022-04-01 20:14 | 2023-02-20 23:45 |
| Reporter | drakinite | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | sometimes |
| Status | closed | Resolution | duplicate | ||
| Product Version | 5.0.3 | ||||
| Target Version | 5.0.3 | Fixed in Version | 5.0.3 | ||
| Summary | 0018958: "Unknown thread" exception after PC wake up on playback restoring | ||||
| Description | User description: "Hovered over the icon to show the miniplayer and then typed in discord" (They did not mean the actual MiniPlayer, they meant the preview that plays when you hover over MM in the taskbar.) They were playing back from YouTube, not from a local file. Cannot reproduce reliably. Log ID: E75F0000 | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 2625 | ||||
|
|
Ludek, does the crash log appear like this one is also related to 0018957? |
|
|
His crash E75F0000 is here and it is External exception E0000008 in libcef.dll i.e. an exception inside of Chromium framework (not in our code). Is it reproducible for him? Also again, if this does not occur with the "MediaMonkey_NoGPU.bat" (like in case of 0018957 ) then attach ouput of chrome://gpu put to the address bar of Chrome browser (in case he is using Edge browser then use edge://gpu/ ) |
|
|
Watching the crash log again and its DbgView part I see this line: 18445.968s - PID:27412 - MM5 [17420](R) MemRAM:_2.7 GB, MemPrivate:_2.9 GB, MemVirtual:_3.5 GB This is abnormal memory usage-- so the exception in libcef.dll could be related to abnormal memory utilization. This would also indicate a memory leak, is he able to still grow memory usage constantly to the values like 2.7 GB ? In that case it would be valuable to see whole log with DbgView started prior to MM start to have a clue where and why the memory grown so high. |
|
|
To be verified whether YouTube playback leaks memory... EDIT: Both Jordan and me played YouTube video for hours without observing a mem leak. So would be still valuable for the user to catch it in the DbgView (in case the user is still able to grow memory to 2.7 GB) |
|
|
BTW: I am unable to replicate, but this one sounds very similar: https://support.google.com/chrome/thread/82011253/chome-freezes-if-i-minimize-then-maximize-the-screen-ie-press-the-little-box-in-top-left?hl=en and disabling HW acceleration in Chrome did the trick. This confirms the user's tests and that it is something between Chromium and GPU. |
|
|
Resolving as dup fo 0018957 as ti sounds very similar and happens for the same user. |
|
|
I got a crash on 2623 after waking my computer from sleep just now. At the same time, Windows Explorer stopped responding (and restarting it from Task Manager would not help). Log ID is E75F0000, the same as in this original issue. However, it almost seems unrelated to this original issue. Perhaps it has something to do with Windows Explorer generally not behaving as MM expected? |
|
|
There is "Unknown thread" exception after wake up when restoring playback via DeviceNotifyCallbackRoutine > handlePowerState > stop > _Bookmark > setPlaybackPos > beginRead > getThreadIndex => Seems a Michal code, but fixed in 2625 by registering it as external thread. i.e. was regression related to the most recent Michal's changes re 0019063 |
|
|
Unable to replicate over 20 tests. 5 sleep during playback / 5 sleep during playback at song transition 5 sleep during pause / 5 sleep during pause at song transition |
