More > JRiver Media Center 29 for Windows

MC29 crashes/stops after few hours of play (not MC28) - 32bit version

(1/3) > >>

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:

--- Quote from: AndreaT on March 14, 2022, 03:11:20 am ---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
--- End quote ---

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:

--- Quote from: JimH on March 15, 2022, 11:38:14 am ---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.

--- End quote ---

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.

Navigation

[0] Message Index

[#] Next page