Crash when launching automatically on CD insertion [#21248]

[Edgar]

MediaMonkey_2024.0.0.3057_Debug

This does not occur all the time – maybe one time in five.

[Edgar]

This may be related:

[Lowlander]

If you can reproduce, please capture this in a debug log (step 4b) and attach the log to a Support Ticket: https://www.mediamonkey.com/forum/viewtopic.php?t=86643

This will help a developer analyze why this happens on your setup.

[Edgar]

Sorry, when this happens MediaMonkey crashes so badly that I must use the TaskManager to kill it. No log files have been created (the folders exist but are empty). Sometimes it gets as far as trying to send an error report but I do not believe that the report is actually sent.

[Lowlander]

That shouldn't be a problem using step 4b. DebugView is what captures everything (you can set to log to file if it or the PC crash too).

[Edgar]

I downloaded and installed the DebugView application. When DebugView is running the crash does not occur (over 10 trials). When it is not running the crash occurred three times out of four. I will try to always run DebugView before MediaMonkey 2024 in the near future. If I manage to generate a crash report, I will send it.

Thanks for the attention!

[Lowlander]

Do you see a MediaMonkey.el file after the crash? If so, please attach that to a Support Ticket.

[rusty]

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

[Edgar]

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

[rusty]

Edgar,

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

Thanks!

-Rusty

[Edgar]

“Rip Audio CD (MediaMonkey)” [2024]

[Ludek]

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 Support Ticket for this issue, I would send you special build that would log the JSON to find what's wrong here..

[Ludek]

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

[Edgar]

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

I would be happy to install a custom debug version.

[Edgar]

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.