As Mac OS X users, we have something to be happy about when it comes to app crashes and freezes: rarity. Typically you can work on your Mac for hours at a time without a single issue. However, a crashing app certainly can happen, leading to lost productivity, time and, worst of all, lost work. Fortunately, there are several steps you can take to recover from a crashed app, as well as prevent the issue in the first place.

R for Mac OS X. This directory contains binaries for a base distribution and packages to run on Mac OS X (release 10.6 and above). Mac OS 8.6 to 9.2 (and Mac OS X 10.1) are no longer supported but you can find the last supported release of R for these systems (which is R 1.7.1) here.Releases for old Mac OS X systems (through Mac OS X 10.5) and PowerPC Macs can be found in the old directory. Sep 29, 2018  The Mac has a reputation for reliability and ease of use, but crashes and freezes do in fact happen from time to time either due to performance-related issues or software bugs. It can be a nasty surprise when your Mac temporarily freezes, or worse still crashes completely (thankfully that’s a very rare occurrence), and you. Apr 08, 2020  The application has also been widely regarded as an app with suspicious privacy policies and corporate data disclosure problems. And only recently, the app has been involved with a new problem – it crashing or freezing during video communications. Zoom App Freezing and Crashing. The Zoom app is made by Zoom Video Communications, Inc.

How to fix a crashing app after the macOS upgrade

App crashes after the the macOS update is more than a common problem. Some apps freeze or malfunction, some won’t launch, some show no signs of life whatsoever. Why it happens? The most probable reason is that the app is simply not ready for the latest macOS Catalina. Something in its depth turned out to be incompatible with the new macOS.

Now, what can you do to fix an app crashing? Three things.

1. First, see if you have the latest version of the app by clicking on its name it the top menu and choosing Check for updates.
2. Second, visit developer’s website (or App Store page) and see if they’ve issued a statement about Catalina compatibility.
3. Finally, some crashed apps on macOS Catalina can be fixed by running maintenance scripts. Download CleanMyMac X, launch it, find Maintenance tab and run the scripts.

What happens when an app craches: under the hood

Now let's go deeper into the nature of crashed apps, but first, let’s identify the difference between a crashed macOS app and a frozen one. While these terms are often used interchangeably, there is a notable difference.

Crash

A crash happens when a piece of software stops working altogether, and then closes on its own. In other words, the app quits when you did not tell it to. When this happens, you'll typically see a message noting that the application has 'unexpectedly quit” just as its windows disappears. It’s pretty frustrating — especially if you end up losing all your work.

Freeze

A freeze is when software stops functioning, but continues to run. You can still see its windows, and its Dock icon still indicates that it’s running. However, no amount of clicking or tabbing around will do anything. A frozen app doesn’t quit like a crashed app does, it simply becomes unresponsive. Often no error messages accompany the freeze. Again, it’s a frustrating experience (if you want to know how to deal with it, check out this post on how to fix frozen apps). Icons missing on apps after mac hard drive updated download.

When software freezes, you force it to quit, so that you can re-launch and hopefully get on with your work. With crashes, meanwhile, the problem is the app quitting on its own. In this article, I’ll discuss recovering from app crashes, as well as steps that help prevent them in the first place. Let’s get started.

What to do when a Mac OS X app crashes

The good news here is that a crashed app rarely brings down your entire Mac, as the trouble is restricted to that particular piece of software. That means we have a chance to recover. Let’s start with the simplest solutions.

First, just relaunch the app. When an app crashes, you’ll typically see a dialog box that says the software “unexpectedly quit” and you’ll have several options to deal with it, including “Relaunch”. Give that a click and cross your fingers that the crash doesn’t happen again. Oftentimes, you’re good from there. If not…

Try restarting your Mac. “Turn if off and back on again” is almost a punchline at this point, but it usually works. Shut down, restart and try again. Very often this simple task will set things right. If not, it’s time to try something just a little more involved.

Why Is My Mac Crashing

Reinstall the app. Deleting the misbehaving app and grabbing a new copy gives you a fresh version to work with. That is, if you delete all of the app’s related files.

See, when you drag an app to the Trash, you aren’t deleting everything. Some leftover parts remain, and if the troublemaker is among them, your problem could persist. It’s a waste of time to delete an app via drag-and-drop, reinstall and then have it crash again. To make things right, you need to get rid of the app’s bits and pieces before you reinstall it, and this is where software like CleanMyMac X comes in handy.

An app that’s simply dragged to the Trash leaves behind a pile of associated files that you don’t see, like caches, preferences (often the culprit in crash-y apps), saved states, and more. You might not even know they’re there, but CleanMyMac X does. It’s smart enough to find the whole lot, safely remove them, and ensure that a newly installed app is just that: a complete fresh start.

In fact, you don’t even have to launch CleanMyMac X to thoroughly and safely delete an app. Simply right-click (or Control-click) the app’s icon and select “Uninstall with CleanMyMac” from Services in the resulting contextual menu. Easy!

Another wise move is to make sure there are no conflicts between the app and the Mac OS. When Apple pushes an update of its operating system to your Mac, that might interfere with your app’s performance, if the app or its add-ons are incompatible with this particular OS X version.

CleanMyMac can help you out here, too. Download it for free, go to its Uninstaller module and find the misbehaving app in the list. If you see a note that this app is incompatible with your system, it means you need to update the app, because your current version doesn’t work on the latest OS X.

How can you stay on top of aging apps? Apple makes it easy with software purchased through the Mac App Store. Simply launch the App Store app, go to the Updates tab, and you’ll see all available app updates. Find the one you need in the list, click the Update button, and you’ll get the latest version to your Mac. It’s a bit different with software acquired outside the App Store: you’ll have to visit the vendor’s website to see if there’s a new version available.

If nothing indicates that the troublemaker app is incompatible with your system, the problem could be with its add-ons or preferences. What you can do in this case is reset the app to its initial state. Again, go to the Uninstaller module in CleanMyMac X, select your app, and click Application Reset. CleanMyMac will make that app just the way it was when you first installed it.

What to do when an app crashes at launch

So far I’ve addressed what to do when an app crashes as you’re using it. But what about the frustrating scenario of an app going down as soon as you launch it? No warning, no dialog box, just a bounce or two in the Dock and that’s it. In this case, it’s time to repair disk permissions.

What’s does fixing permissions actually mean? Think of your Mac’s hard drive as a tree with many branches. The top level of your drive is the tree’s trunk, and the branches represent information about files and folders. These branches, or “nodes,” store information like the location of data and permission rules, among other things. Normal computer use changes this information, and can lead to a conflict or other issue that generates crashes and the inability to use your system. This is what a permission fix addresses.

To repair disk permissions (for OS X prior to El Captian), go to the Utilities in your Mac’s Applications folder and launch Disk Utility. Next, click First Aid. It’ll ask for confirmation and get to work, comparing existing permission files with defaults to find any conflicts.

Or, if you want a slightly simpler way, you can fix the permissions with CleanMyMac X Maintenance Scripts. Just open the Maintenance tab, hit Choose Tasks and then Repair Disk Permissions. This helps resolve improper app behavior like crashing and keeps all of your disk’s files and folders in proper order. And that’s just one of the maintenance tasks available in CleanMyMac X, just try it.

A crashing app is no fun. Fortunately, a little understanding and proactive behavior can keep them to a minimum. CleanMyMac X makes it easy to do just that. Happy computing, and may your apps never crash again!

These might also interest you:

This article’s focus is on macOS crash reports. More specifically this article explains how you can (1) locate crash logs (2) and read them to diagnose a crash.

Your Mac can crash, rarely. These crashes usually mean nothing important, if it is rare. Thus it is not something you should worry about. In most cases, restarting your Mac will resolve the issue. Your Mac will automatically reboot itself.

However, if your Mac is crashing frequently, you may want to find our why these crashes occur so that you can prevent them from happening again. And the most important thing you should do is to find more specific error details.

In this article we are going to take a look at using the crash logs that your system generate. These logs will help you identify what’s causing the crash.

See also: How To Use Network Utility on Mac

Where to find crash reports

There are two ways to access your crash reports. You can use any of the methods:

1. You can use the Console app. The Console app included with your Mac. You can open this app by going to Applications > Utilities > Console. You can also use Spotlight to access Console. Select your Device and click Crash reports under the ‘reports’ section.
2. You can also find your crash reports in ~/Library/Logs/DiagnosticReports/. Here is how you can access there:
   1. Go to Finder
   2. Now press the Option key and then click Go (while you are pressing the Option key)
   3. Click Library
   4. Click the Logs folder
   5. Click the DiagnosticReports folder
   6. And open the file that says “Crash”

See also: Restart your Mac in Safe Mode

How to read macOS crash reports

Understaing these reports can be difficult as they are usually big. Here is how you can decipther a crash report:

1. The first section of a crash report includes what process crashed. Something like this:

In this case, said process is WebKit (Safari).

2. The next section of a crash report includes date/time and operating system, like this:

3. The next section includes more crash details (The Exception), something like this:

Note taking app with pdf annotation mac free. There are four common exeption types, according to Apple:

EXC_BAD_ACCESS/KERN_INVALID_ADDRESS — This is caused by the thread accessing unmapped memory. It may be triggered by either a data access or an instruction fetch; the Thread State section describes how to tell the difference.

Mac Crashing On Startup

EXC_BAD_ACCESS/KERN_PROTECTION_FAILURE — This is caused by the thread trying to write to read-only memory. This is always caused by a data access.

EXC_BAD_INSTRUCTION — This is caused by the thread executing an illegal instruction.

EXC_ARITHMETIC/EXC_I386_DIV — This is caused by the thread doing an integer divide by zero on an Intel-based computer.

The next section includes backtrace information. There can be one or multiple threads. In reverse chronological order, each thread shows the series of events .

To understand this section, find the thread that crashed. You can easily find that, because the report will say something like this: Thread (thread number) Crashed. This section explains what lead to the crash.

Like this:

There are four columns here:

• The first one is the frame number (reverse chronological), like 0, 1, 2, 3….
• The second one is the name of the program or other process that performed the task. In this instance, com.apple.WebKit.
• The third column is the counter program address.
• The fourth column is the task.

From this example, we know that, for example, “com.apple.WebCore 0x00007fff3e26977a WebCore::HTMLMediaElement::mediaCanStart(WebCore::Document&) + 90” is responsible for the crash.

Now you know what caused the crash and series of events triggered the crash. This will help you idendify the problem and then address it appropriately.

If your problem is a third-party app, you may want to contact its developer. Tell them your problem and you may want to send a copy of this crash log. You can click the share icon in the Console app to send the report.

Software Crashing Windows 10

See also: