Help Deciphering Crash Reports
Hello,
Can anyone help me decipher some crash reports from a patch that is going down without provocation at various intervals?
Crash Report 1
Crash Report 2
Crash Report 3
Crash Report 4
The patch is a bit too complicated to post here. Simplifying the patch is particularly tricky. If anyone is able to help decode any useful info in the reports, I'd be extremely grateful :)
My details:
Max 8.1.11
MacOS 10.14.6
I am very far from being an expert in this. What I understand from the reports is that there is a problem with memory allocation. Are you using any 3rd party externals?
Jan is correct,
You'll want to hone in on the
Exception Type:
Exception Codes:section of the report.
Crash 1: EXC_BAD_ACCESS (SIGSEGV)
Crash 2: EXC_BAD_INSTRUCTION (SIGILL)
Crash 3: EXC_BAD_INSTRUCTION (SIGILL)
Crash4: EXC_BAD_ACCESS (SIGSEGV)
Program tried to access a memory address that it should not.
CPU is being given an instruction that it does not understand. Given the recent Architecture change by Apple, this might be a flag that something compiled for ARM is being called by Max on your Intel MacBook.
I might even hazard a guess it is a universal binary and something from the ARM slice is accidentally being called, but it is sort of moot.
A recently updated 3RD party package would be my first thought. Uninstall / Deactivate all of them and add them in one by one to identify the troublemaker. If you have no package installed and active, then it will be something with Max itself.
extra info
https://developer.apple.com/documentation/xcode/diagnosing-issues-using-crash-reports-and-device-logs#//apple_ref/doc/uid/DTS40008184-CH1-EXCEPTION_INFO-BAD_MEMORY_ACCESS__EXC_BAD_ACCESS____SIGSEGV____SIGBUS_
Reading crash reports
https://www.cnet.com/tech/computing/tutorial-an-introduction-to-reading-mac-os-x-crash-reports/
https://www.maketecheasier.com/read-macos-crash-reports-troubleshoot-mac/
Thank you both! I believe I've solved it. At your suggestion, I removed all 3rd party externals, restarted the machine, and was able to create a crash. That crash report indicated pictslider, which I was using extensively for animation purposes in the patch. I adjusted the message handling going into pictslider and that appears to have fixed the issue. I'm not sure of the impact of 3rd party externals, but I'll keep an eye out for similar behavior going forward.