

Reading crash reports is a specialised business, and normally needs insight into the workings of both macOS and the app which quit. Unfortunately, in most cases – whether it quit of its own accord, or was forced to by macOS – all you will see is a crash report, which may invite you to re-open the app, or to send the report to Apple.
APPLE MAC HANG UP CODE
If this happens when the app is trying to start up, for example, it could be because there is a signature error, it tried to access privacy-protected resources to which it wasn’t entitled, or a problem with the app’s code or files. There are also several reasons for macOS forcing your app to quit suddenly. Restarting your Mac normally clears that. So although you should be safe to continue working, and reopen the app which quit, be aware of any signs of odd behaviour indicating residual damage. When an app unexpectedly quits, macOS and all your other running apps should be unaffected, but sometimes the app, when on its way out, leaves some damage to macOS, files in storage, or elsewhere.

There’s then likely to be a period during which the app’s developers blame Apple, Apple says little, and eventually the problem is quietly resolved. Of course this isn’t necessarily a matter of blame: many of these bugs occur when the app expects macOS to do something one way, and it doesn’t.

If an app consistently quits unexpectedly when you try doing the same thing, you can be fairly confident that it’s a bug in that app, and should report that to the app’s developers. Unexpected quits can happen for many reasons, but the most frequent are bugs in that app. This normally results in that app suddenly quitting, so is most often termed an unexpected quit. So the most common type of ‘crash’ should be one app biting the dust when it has done something wrong. Each app runs in its own separate space, kept apart from other apps, and from protected system space. MacOS has protected areas, including the kernel itself, which apps shouldn’t be able to affect.
APPLE MAC HANG UP HOW TO
That’s a succinct term, but not very useful when you come to work out what went wrong and how to fix it. When your Mac goes wrong, it’s often called a ‘crash’.
