MediaMonkey forum

Twice today I've had an 'Access violation' pop up.

Latest ID=06300000

Please capture these types of errors in a debug log (step 4b) and attach the debug log to a Support Ticket: https://www.mediamonkey.com/forum/viewtopic.php?t=86643

If I knew when the error would happen I would do so, but given that it can take several hours to days before the error happens, it is not really practical.

Unless you know of some way of retroactively capture the debug log info?

Ran for just over a day before it crashed again. The next two instances crashed within hours of being started.

Another log ID: 66F60000

And another: 66F60000

Another one, in the middle of the night.

ID=06300000

After two hours: 06300000

This release is way too unstable. I'm reverting back to 3018

Could you please test whether you are still observing this issue with build 3021:
https://www.mediamonkey.com/forum/viewt ... 86639&sd=d
?

3021 doesn't work for more than a couple of minutes.

A new error: ID=6CA60000

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

lindholm wrote: ↑Mon May 20, 2024 10:42 pm 3021 doesn't work for more than a couple of minutes.

A new error:

Code: Select all

A breakpoint has been reached.

Code: 80000003 (EXCEPTION_BREAKPOINT)
Address: (034844BD)(libcef.dll) [132F44BD] + $0

ID=6CA60000

This sounds more like a system/driver/hdd error, please try the tips from here:
https://www.auslogics.com/en/articles/f ... x80000003/
to see which one helps to resolve the issue?

None of them apply.

And the error has only occurred once so far so I can't see how it can be a system issue since it would be repeatable in that case

Aside from the initial glitch, things are looking better.

MM has been running for five days now (a new record)

Never mind

Had to restart MM after reboot. Crashed after a couple of hours

It took 42 minutes this time.

Back to 3018