MediaMonkey forum

I am still getting the "White Screen of Death". All I have to do is open MMW and it automatically starts to monitor folders and analyze volume levels. At some point, usually hours after the start I get the white screen of death.

Is this still a known issue? Do you 'need' a debug dump from me? Please be aware even zipped up to its smallest size it will be huge (many GB in size).

Greg

Which build of MediaMonkey?

Sorry should have said that up front. 2027.0.0.3517

FYI I have over 90K tracks on a NAS. The white screen takes several hours before it comes up.

Greg

Please capture this in a debug log (step 4b): viewtopic.php?t=86643

Hi,
I just finished 5h run to scan my NAS files around 150k and no crashes.

Right now not getting any crashes I will get you a debug log as soon as I can get MMW to crash again.

Greg

I got the white screen of death again. This time I got the usual MMW error box, which I sent and an additional windows error saying "Out of memory".

At the time this happened MMW was updating several 10's of thousands of track properties, and associated database entries. This happened somewhere between 5 and 17 hours into the updates.

Greg

I am on MMW 2027.0.0.3521 and still getting the white screen of death. Once in a while I will get an option to send the logs, less often I get a different message (maybe from Windows) saying I am out of memory. This is happening, it seems, what MMW is monitoring and updating itself.

Is this still being run down?

Greg

Please capture this in a debug log (step 4b): viewtopic.php?t=86643

Log capture started. Two questions how large can the log get, and where is it stored? Need to make sure there is enough space.

Greg

Depends on how long it runs, and how much you're doing in MediaMonkey. It's not stored until you save it.

Updating my entire library. One of the logs was over 17 MB when I saved it, the time from start to white screen can take a dozen or more hours of work before it happens.

While I am working in MMW, MMW is; Monitoring, Analyzing Volume, Scanning. Each one seems to be dealing with between 10k and 100k files each. A lot of the white screen happens over night when MMW is doing what it does over night.

Greg

Who would have thought when we want a log a log would be provided in a timely mannor. While I was typing out the last message, white screen of death. Log file is here: https://www.mediafire.com/file/zyrcb5g3 ... 4.rar/file

Sadly log does not show any information about crash, only sudden end of renderer process. Also DbgView has to be started before MM, otherwise it does not contain all messages. Next build should show us slightly more, I also fixed there more memory leaks, so hopefully it will behave better.
Btw. are there any new MediaMonkey*.el* files in C:\Users\Kurby\AppData\Roaming\MediaMonkey5\?

Not sure if this helps. I ran for 18-24 hours, no white screen. The major difference was when MMW started I canceled the 'Monitoring' and 'Analyzing Volume' tasks.

Greg