Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[AndreaT]

Hello,
I upgraded from MC28 .106 32bit version to the new MC29 and I noted that MC29 crashes/stops (quite often) after 2-3 hours of continuous play (to know that I use random generated playlist/smartlists).

To be noted that "no crash report is generated". I just have unexpected MC29 shutdown. And restarting it, the playlist is correctly presented where it left...

Regards, Andrea

[Vocalpoint]

To be noted that "no crash report is generated". I just have unexpected MC29 shutdown. And restarting it, the playlist is correctly presented where it left...Regards, Andrea

This happens to me all the time (in MC20+) and it's always something to do with not being able to play a specific file at a specific moment in time.

MC never displays any useable info on what is wrong (if anything) - and when I fire up MC again and hit the same file again - of course it plays fine.

Have never been able to figure out what MC does not like about a specific file at any given time.

VP

[JimH]

If MC is having trouble opening a file, then there is probably something wrong underneath (at the OS level).  Antivirus software is the usual suspect but it could be drive related, etc.

Did you configure Windows Defender?  Are you using any other AV?  If so, uninstall it.

Turn on logging and see what's near the bottom of the log.  Look for the file name.

The current log will have the information unless MC has crashed, in which case it will be in the previous log.

We've talked about this in the past.  I don't think there is a generic MC problem.

[Vocalpoint]

If MC is having trouble opening a file, then there is probably something wrong underneath (at the OS level).  Antivirus software is the usual suspect but it could be drive related, etc.

Everything here is properly configured and MC is isolated from any and all AV. I agree - I do not think this is a generic issue but conversely - the error message is horribly generic.

Logically - in the code - there must be a very specific technical reason why MC suddenly cannot play a file - that reason (whatever it is) should be put on screen as encountered. At least then the user would have some idea where to start troubleshooting.

What we really need is a message saying "why" MC has encountered the error so the user can investigate. Even something simple like "File was Locked for Read" or "Header error in FLAC file" or "File Share Unavailable" are infinitely more valuable than saying "MC has encountered an error when playing file" - which is blatantly obvious as the app has already crashed and stopped.

Hoping you could consider something like this for a future release.

Cheers

VP

[Matt]

If you get a crash, please share a crash dump.

[Vocalpoint]

If you get a crash, please share a crash dump.

Matt

Where would/does MC store a crash dump? Or are you talking an OS dump?

Please advise.

VP

[Matt]

Click "Report Problem" after a crash:
https://wiki.jriver.com/index.php/Logging

[Vocalpoint]

Click "Report Problem" after a crash:
https://wiki.jriver.com/index.php/Logging

Will do!

Thanks.

VP

[AndreaT]

If you get a crash, please share a crash dump.

I always let Windows reporting the Crash to Microsoft. Is this what you want or other?

To be noted that in my case the crashes happen also during the play of an audio file, so not only when trying to open a new file

[Matt]

You need to share the crash report here if you want us to help.  Click "Report Problem" after you restart.  Thanks.

[AndreaT]

You need to share the crash report here if you want us to help.  Click "Report Problem" after you restart.  Thanks.

OK, sorry, I didn't understand well the process. I will do so.

[AndreaT]

You need to share the crash report here if you want us to help.  Click "Report Problem" after you restart.  Thanks.

Here you are 2 logs of crashes of today.

[Matt]

Here you are 2 logs of crashes of today.

Unfortunately neither of them contain a crash dump.

It's working on sorting files and gets swamped in both logs.

Is that something I could reproduce if you sent me a library backup?  I'm matt at jriver.

Thanks.

[AndreaT]

Unfortunately neither of them contain a crash dump.

It's working on sorting files and gets swamped in both logs.

Is that something I could reproduce if you sent me a library backup?  I'm matt at jriver.

Thanks.

Hello Matt, this is a right now crash

[Matt]

We need a .DMP file for the log to be helpful.

But could you send me your library and instructions on how to make it crash?  It's sorting and getting buried.  I can't explain why without a library though.

Thanks.