View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015255 | MMW 5 | Main Panel | public | 2018-12-12 12:08 | 2019-01-10 02:16 |
| Reporter | Ludek | Assigned To | |||
| Priority | immediate | Severity | crash | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0015255: Renderer process crashes (white screen remains) | ||||
| Description | In the recent builds the renderer process (MediaMonkeyEngine.exe) sometimes crashes and only white window remains. No crash log is generated. It is reported by users on the forums, by Rusty in 0015248, and I have reproduced it once too. It seems that this can happen randomly during some extensive operations like scanning or syncing, but I reproduced it just by reading GPM tracklist (of 10K tracks) several times and then switching to Music > All tracks | ||||
| Additional Information | http://www.mediamonkey.com/forum/viewtopic.php?f=30&t=90486&start=75#p453526 http://www.mediamonkey.com/forum/viewtopic.php?f=30&t=93390 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2140 | ||||
|
|
Just reproduced this again by switching from Devices & Services > Google Play Music > All tracks to Music > Albums while the GPM tracklist wasn't read completely yet. Debug logs: https://www.dropbox.com/sh/ca6lttnmxlwh521/AACiQaBM4EgWnVMeHj_m69K2a?dl=0 EDIT: I haven't found any clear pattern yet, it just happened nearly after start upon switching from [Music > Albums] to [Playlists > Accessible tracks] (log LUDEK-NB-PC 3) |
|
|
The more I am testing this the more the problem seems random. Sometimes it crashes after 25 seconds, sometimes it takes more than 5 minutes to crash. The debug log ends with different messages everytime. The only common thing is that before the crash UI is frozen for at least 3 seconds (sometimes even more than 15 seconds) and then the MME process disappears (white window remains) like if someone kills it. No crash log generated. |
|
|
I don't know what has happened, but I am unable to replicate anymore. |
|
|
Petr has found one place in chromium where process kill is called. He disabled it for the build 2140 -- so we will see whether it will solve the issue (or at least crash log will be generated). |
|
|
Verified 2143 while testing it for 25 min |
|
|
Haven't seen this occur in recent builds. Closing. |
