The problem still occurs – maybe once in twenty times <shrug>. I have never gotten it to happen when DebugView was running.
[url=https://ibb.co/3dNprW5][img]https://i.ibb.co/7CWnYVx/MM29-October-2024.png[/img][/url]
there may be one or two logs submitted sometime just before noon on 29 October 2024.

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

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/fix-breakpoint-error-0x80000003/

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

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)
[url=https://ibb.co/5hgCKBt][img]https://i.ibb.co/jkPqJgB/Media-Monkey21-October-2024.png[/img][/url]
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>.

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

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

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..

I just tested MediaMonkey_2024.0.0.3059_Debug
I could not reproduce the bug – I cannot be 100% sure whether it is the new build or the fact that I renamed both of the MediaMonkey AppData folders to get a completely fresh start <shrug>. Additionally, during the entire series of tests I had “DebugViewer” running.

The first test I performed was to insert a CD, thus forcing MediaMonkey 2024 to launch in ripping mode. This worked fine and I canceled out of the CD ripping window and immediately shut down MediaMonkey 2024. I repeated this sequence more than five times (but fewer than ten times) – in the past, this would certainly have triggered the problem.

I consider the issue resolved.

Ticket #7653: "Crash when launching automatically on CD insertion" has been successfully submitted

I would be happy to install a custom debug version.

Or at least I would need to get your persistent.json file for analyzing, could you please open the ticket and share the file?
It is located in %APPDATA%\MediaMonkey5\persistent.json

Hi,
I see your log A14AC18C here..

Your description is "Choose “eject CD” from context menu",
but it the log I see that the MediaMonkey got WM_CLOSE message and was actually closing (and there was an exception when trying to pretty-print persistent.json file), still analyzing why this could happen..

Are you sure that you haven't initated closing of the MM5 window (either by mouse or by keyboard) and you just selected the 'Eject CD' action?

EDIT: Could you please open [url=https://www.mediamonkey.com/support]Support Ticket[/url] for this issue, I would send you special build that would log the JSON to find what's wrong here..

“Rip Audio CD (MediaMonkey)” [2024]

Edgar,

One other question, is your system configured to Play the CD on insertion OR to Rip the CD on insertion?

Thanks!

-Rusty

As I said earlier, it does not happen every time I start MM 2024 – but it is quite frequent.
The image in the first post occurs immediately when MediaMonkey launches automatically after insertion of a CD. The image in the second post occurs after ripping a CD – I think this one is related to closing the CD ripping window.

I am running on an up-to-date Windows 10 desktop computer with lots of CPU cores and RAM. This was not happening with MediaMonkey_2024.0.0.3005 (I missed a number of updates until MediaMonkey_2024.0.0.3043). I think it started happening in 3043 or 3051. I will be running DebugViewer before launching MediaMonkey for the near future – might get better details <shrug>.

hmm.... I'm unable to replicate this either. Does the crash occur as soon as you insert the CD and MM launches?

OR does it occur subsequent to launch when the Rip CD dialog appears OR when the metadata for the CD is looked up?

Thanks!

-Rusty