MM 4.1.31.1919, WIndows 11, 64 gigs of RAM.
When started: moved all my music to another drive. The feature to locate missing files did not really do anything.
Decided to clear the DB and create a new one. Since then it keeps quitting.
It monitors/scans the files. As soon as it is done, the bar says "Monitoring" for a few seconds, and then MM exits without any error code.
I tried to switch to MM5 number of times but it could never complete scanning the DB (450K plus files) and would gert stuck or crash. MM4 was working fine
Unchechked to scan on startup (left "scan continiously" checked), it does not quit.
Is there something I am doing wrong?
MM quits after completing the startup scan
Moderator: Gurus
Re: MM quits after completing the startup scan
Hi,
Only thing I can suggest unless you want to switch to MM5 and try is to Create full debug log as described at https://www.mediamonkey.com/forum/viewtopic.php?t=69 and supplu DL link to it in support Ticket.
Such sudden crashes often means bad.corrupted file that crashes whole MM and kills process without warning. Log file should show which file is in question.
Only thing I can suggest unless you want to switch to MM5 and try is to Create full debug log as described at https://www.mediamonkey.com/forum/viewtopic.php?t=69 and supplu DL link to it in support Ticket.
Such sudden crashes often means bad.corrupted file that crashes whole MM and kills process without warning. Log file should show which file is in question.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
How to attach PICTURE/SCREENSHOTS to forum posts
Re: MM quits after completing the startup scan
Thanks so much.
Just a quick update. Ended up nuking the DB and creating it again.
Looks like this did a trick. No more crashes like this.
I am contemplating giving v5 another try now.
Just a quick update. Ended up nuking the DB and creating it again.
Looks like this did a trick. No more crashes like this.
I am contemplating giving v5 another try now.