Print

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

[bigwilly]

Have been using Media Centre 20 for a couple months without a hiccup.

Not sure what happened but now it constantly crashes and I get the "Media Centre Quit Unexpectedly"
The first instance was when I was playing music
My media is connected via network NAS.

I tried the following,
Updated to most current version
Reboot Mac Mini
Renamed Library to Library1 and rerun file import  - another crash took place during scanning and uploading (the scan can never fully complete, tried running a couple times)
Reboot NAS
Reinstalled Mac OS and everything up to date
Options > Tree & View > Advanced > Display missing file image in lists: Disable

Log is attached, thanks for help.

[bigwilly]

Attached another log file I found in case it may also help.

[bigwilly]

Tried also "Auto Import Off"

Ran import folder to rebuild library - crash again.

[JimH]

Try testing a local library to see if the problem could be related to the NAS drive.

[bigwilly]

Figured it out.
There was an incomplete music album I added recently that had not completed downloading.
For some reason this was causing the player to crash.

I deleted the album and no crashes so far.

[JimH]

How was it being downloaded?  From where?  With what?

I'm just asking in case other people are affected by the same problem.

[bigwilly]

Torrent with vuze. Flac files.

When the player tried to add those files to the library (either auto import or running a scan) the player would crash.
Deleted the files was the solution.

[JimH]

Thanks.

[alerutte]

May I ask how you found the offending file? I'm having the same problem.

[blgentry]

I suspect bigwilly thought about the last few sets of files he added to JRiver and removed them.  But I'm just guessing.

If you are trying to find bad files that make JRiver crash, I thought turning off Auto Import was supposed to stop it from happening.  But that's just what I've read here several times.

Let's assume for a moment that you definitely have a bad file that's causing crashes.  Binary search is probably the most efficient way to find it.  Though it could take a good number of tries to isolate the bad file, depending on how many files and folders you have.  Binary search is essentially cutting the collection of files and folders IN HALF at each step.  So it isolates the offending files pretty quickly.  This would require some determination to do correctly.  It could be 15 or more trials, depending on exactly how you do it and how many files and folders are in your collection.

Maybe it would be smarter to figure out the last 5 or so sets of files you've added to JRiver and eliminate those first.

Good luck to you.

Brian.

[tortuga_Bob]

Figured it out.
There was an incomplete music album I added recently that had not completed downloading.
For some reason this was causing the player to crash.

I deleted the album and no crashes so far.

Sorry to butt in here but I thought I could provide a useful tip. I have also been plagued by corrupt Zip files (don't know if yours was a Zip or not). I have found that expanding these Zip files using the Finder results in a set of bad files that is not flagged in anyway. I now only expand Zip files using a dedicated app such as Stuffit Expander. Stuffit Expander will report an error if there is something wrong the the downloaded Zip file and not expand it. If the file is expanded then you can be pretty confident that it is a good download.

[JimH]

We'd appreciate it if you could provide a sample file that causes a problem.  Thanks.

[tortuga_Bob]

We'd appreciate it if you could provide a sample file that causes a problem.  Thanks.

If you are asking if I have one of the corrupt Zip files, then the answer is no, there would be no reason to save them. I did not say that one of these files caused MC to crash, just saying that a corrupt Zip file could lead to the incorporation of bad files into MC unless some kind of verification process is used. I don't know what the source of the "bad" file was for the OP.