More > JRiver Media Center 30 for Mac
MC crashes again
blgentry:
MajorCyco: You should turn on logging as described in the wiki link. Then submit the MC log here after your next crash. That should have some good diagnostic info in it to help the team identify the problem.
Brin.
bob:
--- Quote from: MajorCyco on May 05, 2023, 12:05:25 am ---Since upgrading to 30.0.93, getting a lot of crashes. Before that, pretty incredibly rare. I have the log, but have no idea how to read it. I did get this from the Problem Report.
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: Media Center 30 [8064]
Path: /Applications/Media Center 30.app/Contents/MacOS/Media Center 30
Identifier: com.jriver.MediaCenter30
Version: 30.0.93 (5773)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2023-05-04 23:32:27.0603 -0400
OS Version: macOS 13.3.1 (22E772610a)
Report Version: 12
Bridge OS Version: 7.4 (20P4252)
Anonymous UUID: DC988ED4-484E-C236-B127-963DD398AE21
Time Awake Since Boot: 49000 seconds
System Integrity Protection: enabled
Crashed Thread: 12
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00002a65dd89bc80
Exception Codes: 0x0000000000000001, 0x00002a65dd89bc80
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [8064]
VM Region Info: 0x2a65dd89bc80 is not in any region. Bytes after previous region: 46611112746113 Bytes before following region: 58936119411584
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
CoreAnimation 157f59000-15eb86000 [108.2M] rw-/rwx SM=PRV
---> GAP OF 0x5ffea147a000 BYTES
MALLOC_NANO 600000000000-600008000000 [128.0M] rw-/rwx SM=PRV
All my files are local and the crashes are random and not recreatable.
Any ideas?
--- End quote ---
Post the WHOLE crash report. It's telling you that it's crashing the Thread 12.
MajorCyco:
Enclosed is my log from today. I kept the log from the day I posted my message, but it is too large to attach.
bob:
--- Quote from: MajorCyco on May 08, 2023, 02:40:47 pm ---Enclosed is my log from today. I kept the log from the day I posted my message, but it is too large to attach.
--- End quote ---
The apple crash report, not the log.
soundritter (Germany):
Good morning (in Germany),
MC just crashed again on exit and no log file was created. Attached is a screenshot of the location in the Finder where the file should be.
Next time I will copy the Apple report and attach it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version