Print

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

[mud_shark]

Hello.  I've been using JRiver for a couple of years now (since version 25).
Over the past couple of days MC26 has been crashing about 40 seconds after I launch the software - whether I play anything or not.

Some background:

- I'm using Windows 10 and am completely up to date.
- I have added the key folders as exceptions to Windows Defender (but am yet to go further down the list of more detailed exceptions).
- I have tried backup, uninstalling, restarting, reinstall, restore library from backup.
- In these cases I always look for what has changed in my environment. in this case, I did consolidate my library which had previously been split across two drives, into one (altogether around 50,000 files). All files appear to have imported correctly. I have also done a clean install of Windows... So a couple of potential culprits.


So I am a little lost as to how to proceed. I have attached my log for reference. Perhaps it can reveal some details to anyone who can decipher it.
Can anyone offer some insight as to what might be causing this, and how to resolve?

Thanks in advance for your assistance. It's an amazing bit of software, so am super hopeful this can be resolved.

[RoderickGI]

It is always best to post the zip file that MC creates when you report logging. It has more information in it, such as the previous log and crash dump file, if one exists. There are only 21 seconds in that log file.

There is no crash in that log.
MC appears to be importing files that are missing, but that shouldn't cause a crash.
Usually, if Auto Import is causing crashes, which it may be, then there are one or more corrupt audio files. If you have just consolidated your library it is possible a file copy corrupted files.

Start MC and immediately turn off Auto Import in the background in Options. Then see if the crashes stop.

[mud_shark]

It is always best to post the zip file that MC creates when you report logging. It has more information in it, such as the previous log and crash dump file, if one exists. There are only 21 seconds in that log file.

There is no crash in that log.
MC appears to be importing files that are missing, but that shouldn't cause a crash.
Usually, if Auto Import is causing crashes, which it may be, then there are one or more corrupt audio files. If you have just consolidated your library it is possible a file copy corrupted files.

Start MC and immediately turn off Auto Import in the background in Options. Then see if the crashes stop.

I have turned off auto-import and the crashing seems to have stopped - so thank-you :-)
Attached is the ZIP of the log file. I hope it provides some additional insight.

If the issue is corrupted files, how do I identify them?

Thanks again..

[RoderickGI]

Well, I can't see any crashes in the logs, and there is no crash Dump file in the zip file. In fact, I can't see any relevant errors. There are some BuyButton errors and what appear to be errors accessing a CD drive of some kind. Also, usually the crash is reported in the "Previous Log.txt" file, as the "Log.txt" file logs the restart of MC required to report the problem.

There are some Thumbnails being built, and some other import processes, such as Audio Analysis. But most of those happen in the "Log.txt" file, whereas with a crash I would expect them in the "Previous Log.txt" file, as above.

Does MC actually crash, which means the MC window disappears completely? Or does MC just Lockup, which means it becomes unresponsive?



Usually, if there is a crash, MC runs a crash process which is recorded in the "Previous Log.txt" file, and it is possible to see the last file touched before MC crashes, which is usually the corrupted file. Depending on the file type, there are also some tools that will check files for corruption to be found on the internet. Usually for MP3 files, but there could be others. Google to find those. But you probably need to know which file(s) to check first, which means creating a log with the crash in it.

You could try turning off Audio Analysis in the Auto Import Configuration, and then turn Auto Import back on again to see if you get the same problem (Crash or Lockup).

[JimH]

This might help:

https://yabb.jriver.com/interact/index.php/topic,126493.0.html

[mud_shark]

Well, I can't see any crashes in the logs, and there is no crash Dump file in the zip file. In fact, I can't see any relevant errors. There are some BuyButton errors and what appear to be errors accessing a CD drive of some kind. Also, usually the crash is reported in the "Previous Log.txt" file, as the "Log.txt" file logs the restart of MC required to report the problem.

There are some Thumbnails being built, and some other import processes, such as Audio Analysis. But most of those happen in the "Log.txt" file, whereas with a crash I would expect them in the "Previous Log.txt" file, as above.

Does MC actually crash, which means the MC window disappears completely? Or does MC just Lockup, which means it becomes unresponsive?

Usually, if there is a crash, MC runs a crash process which is recorded in the "Previous Log.txt" file, and it is possible to see the last file touched before MC crashes, which is usually the corrupted file. Depending on the file type, there are also some tools that will check files for corruption to be found on the internet. Usually for MP3 files, but there could be others. Google to find those. But you probably need to know which file(s) to check first, which means creating a log with the crash in it.

You could try turning off Audio Analysis in the Auto Import Configuration, and then turn Auto Import back on again to see if you get the same problem (Crash or Lockup).

The problem appears to have resolved since I turned off Auto-import.
For clarity, it was actually crashing - every time, 40 seconds after MC launched. The window disappeared completely.

I can't explain it  - but am simply happy that everything seems happy again. I have a much clearer picture as to what information I need to capture should this happen again.

Sincere thanks to those who offered support. Cheers.

[Awesome Donkey]

If it's crashing during auto-import, you've probably got bad files somewhere which when MC tries to import them, it causes MC to crash.

Basically if you enable logging and cause MC to crash again and look towards the end of the log for media files, then move those files out so MC won't import them, it might fix the issue with auto-import.