How to investigate an app that crashes when starting up, using log entries. Includes detailed instructions for one of the simplest adventures in the log, and a summary of code signature errors.
crash
When an app can only run for a moment, it might seem hard to work out why it crashes. Here are useful clues from the crash log and elsewhere to help you get the app running properly.
Distinguish between panics, freezes, app crashes, and unresponsive apps, as they have different causes, are investigated differently, and have different solutions.
Why is that app slow to launch, unable to update itself, generally behaving erratically, and often crashes? Could it be stuck in app translocation? Here’s how to tell, and how to fix it.
How to save the panic log safely. Looking up the immediate cause of the panic, getting OS details, what to see in a memory leak, what task resulted in the panic, and 3rd party kernel extensions.
One cause of an app crashing as soon as it’s launched, these constraints prevent you from running bundled apps copied elsewhere, and can now be used by third-party apps.
How we crashed and burned with the best of them, from recovery disks in classic Mac OS, to unexpected restarts and hidden panic logs.
Why won’t Ventura let you run a copy of one of its bundled apps, and why does it refuse to run some command tools?
Causes include code signature errors, app translocation, damaged documents, and corrupted or incompatible preference file.
Using the correct term gets us half way to a diagnosis: kernel panics, freezes, app crashes and unresponsive apps are distinguished here.
The Eclectic Light Company 