More > JRiver Media Center 25 for Mac

Crash

<< < (2/4) > >>

RoderickGI:

--- Quote from: normd on December 08, 2019, 04:41:31 pm ---Any suggestions on how to identify a "bad file"?
--- End quote ---

Turn on logging in MC, if you can before a crash happens. The log will shows which file was being imported when MC crashed. If you can't turn on logging before a crash, move the most recent files you added to a location Auto Import doesn't watch, then run MC and turn on logging. Then move the files back, or use the "Import a Single folder" function to try to import the suspect files, and if you get a crash, restart MC and look at the logs.

There are also tools to identify and fix corrupted audio files. Google "check audio files for corruption" or similar. Just be careful about which solution you select, if using a third-party tool.

dichotomous1:
I never stated anything about auto-import.  It was crashing within seconds of startup, without enough time to change any settings.

Since my original posting, I had several issues going on with the Mac so I wiped it clean and installed a fresh OS instead of using the time-machine restore as before.

I've now reinstalled MC with the most recent stable build.  Same problem, but now it takes a few more seconds before crashing.
If the app didn't crash before my reinstall, why would a corrupt file cause out after a reinstall?

I'm assuming the SMART functions of MC are automatically connecting to my NAS and loading the music library stored there, am I correect? 
Again, the same NAS library is currently loaded in my MacBook Pro.  It loads and plays fine, no crashing.   

Because I am unable to get the app to stay up enough time to turn on logging nor turn off auto import, I have attached a text version of the info provided in the Apple crash report if it helps.

Thanks. J

Awesome Donkey:
Those type of crashes have been happening lately, mostly due to issues with trying to get MC notarized for macOS Catalina and Xcode 11 causing issues.

Looks like the latest build was "downgraded" to 25.0.113 because of all those issues: https://yabb.jriver.com/interact/index.php/topic,123301.0.html

If you're running Catalina, do mind the known issues part.

dichotomous1:
Was able to move fast enough to turn off auto import and turn on logging.  Attached is the log.  I don't see anything regarding specific files.

Also, I don't know if this is related at all, but when I added MC to the approved list for Accessibility in System Prefs/Privacy.  Next to the MC logo where the app name list, it has "package installer" in place of Media Center 25.

dichotomous1:
Not on Catalina.  This iMac 2009 only supported up to High Sierra.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version