Print

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

[dburna]

I have a problem with recurrent crashes with MC22 on my Mac Mini.  Usually this happens when I am not performing any tasks....or even viewing any files.  Typically happens within 1-2 minutes of startup -- could it be a startup activity?

Anyway, I would appreciate any help.  I have enclosed a log from the latest crash.

Thanks in advance,  -dB

[JimH]

Try turning off auto-import under Tools > Import.

[dburna]

Wow -- such fast service.   

I turned off auto-import as well as import of empty libraries (or whatever that second option is).  Seemed perfectly stable at that point......until I tried to run a manual import, then it crashed. 

So, is this a known problem with MC22 (Mac) and importing?

Regards,  -dB

[JimH]

Maybe a bad file.  Make sure you're running the latest build from the top of this board.

[dburna]

22.0.43 -- that is the version I am running.  I guess I will either need to find the offending file and/or wait for the next release.

Regards,  -dB

[JimH]

It would be good to find the file.    You can try importing from some folders and not others.  Or change your settings to import some file types and not others.

If you find the file, we would like to see it.

[dburna]

Will do.  So far I am removing those files that are flagged bad by JRiver, but I haven't found anything that crashes the whole app.  Just a matter of time -- I am pretty relentless about this.   

-dB

[dburna]

Update: things get stranger.  I have music on three hard drives.  When I import them singly (import single folder which in this case is the root level of each drive), no problems.  When I try to auto-import the whole three drives, it crashes. 

Hmmmmmmm.......

[blgentry]

Crashes of MC, from importing bad files are a relatively well known phenomenon.  Nothing mysterious about it.  MC reads the bad file and it crashes.  Here's how to troubleshoot these problems:

Enable Logging.
Wait for the crash to happen.
Use "report problem" in the Logging dialog to collect a log zip file.
Examine "previous log.txt" in the zip file.  You will probably find the name of the bad file at the very end of the log file.
Remove this file from the auto import directories (move it to another location).
Repeat.

Usually a few rounds of this locates all of the bad files and then MC is happy to continue operation as normal, as long as you only feed it good files.

A little bit of reference material on the logging process:

https://wiki.jriver.com/index.php/Logging

Good luck,

Brian.

[dburna]

Found the offending file.  Wish JRiver would crash more gracefully, but hey.......

File (MP4 video) is nearly 1GB, so it's unlikely I'll be able to send it to anyone.  It seems to be corrupted -- I can no longer play it.  Let me know if you want it Dropbox'ed.

Don't understand how this has happened, but MC22.0.43 has been crashing only in the last week or so.  I haven't touched the offending file in maybe 3 years, so it's not clear to me a) how it got corrupted and b) why MC22 picked this particular time to choke on the file.  Odd.

Thanks,  -dB