Crash when launching automatically on CD insertion [#21248]

[Ludek]

Hi Edgard, thanks for subitting the files via [Ticket # 7653]
I replied via the ticket and supplied the new EXE with ability to save the JSON in case of syntax error (just in case you could replicate this again..). Note that this happens only when testing the _debug_ build.. I'll add this to the future builds too..

[Ludek]

FYI: Finally found the cause and is fixed as https://www.ventismedia.com/mantis/view.php?id=21248

[Edgar]

After extensive testing of MediaMonkey 3062, I believe that this issue is now resolved and have close the ticket.

[Edgar]

I just installed 3064 and, the first time I tried to automatically launch/rip with inserting a CD…
I got a different crash (although I suspect that it is probably a similar trigger)

there should be one or two logs in your queue dated 21 October 2024, shortly after 16:00 Pacific standard Time (4 PM).

The first was a “Breakpoint reached” it almost completely disabled my computer and the only thing I could do was to use Task Manager to eliminate it. Shortly thereafter the second popped up. Unfortunately, DebugView was not running. Without rebooting, I started DebugView and tried to re-create the problem without success. I then rebooted and started DebugView and again tried to re-create the problem but have not had any success.

I suspect that the ticket might have been prematurely closed <shrug>.

[Ludek]

Hi Edgar, we have received the second log (freeze log in ntdll), but it was just consequence of the first "A breakpoint has been reached" exception 80000003 in libcef.dll that failed to submit (0A500000) that was a crash in Chromium engine..

This sounds more like a system/driver/hdd error, could you please try the tips from here:
https://www.auslogics.com/en/articles/f ... x80000003/

But I guess you saw this as one time error that you are no longer able to replicate?

[Edgar]

I was only able to retest five times and I never saw the problem again. Probably one-time or extremely rare.

[Edgar]

The problem still occurs – maybe once in twenty times <shrug>. I have never gotten it to happen when DebugView was running.

there may be one or two logs submitted sometime just before noon on 29 October 2024.