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.
Some users were able to stop the Photos app from crashing by restarting their computers. Many Windows 10 users also fixed this issue by simply closing and restarting the Photos app. Here are the steps to solve 'The Google Photos app Crashes when I Enable Backup on a Specific Folder' Issue: Delete the App-data of Google Photos app. Do the same for Google Play services and uninstall the updates of Google Photos app. Restart the phone and update.
Reboot Your iPhone to Fix Crash. In most of the situation, reboot your iOS device can be helpful to. Restart Photoshop. “Turn it off and back on” is the most common tech support tip for a reason: it.
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.
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).
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.
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:
Every time I open Photos, it crashes immediately. I can view my library fine on my iPhone and iPad. It's only on my MacBook Pro that this is happening. Here is the first 100 or so lines of the crash report. I tried deleting all the folders in thumbnails as was suggested elsewhere on the board, but that didn't work either. Any suggestions?
Thanks, Tammy
Crash Report:
Process: Photos [12917]
Path: /Applications/Photos.app/Contents/MacOS/Photos
Identifier: com.apple.Photos
Version: 1.5 (370.42.0)
Build Info: PhotoApp-370042000000000~1
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Photos [12917]
User ID: 501
Date/Time: 2016-04-04 16:47:44.840 -0500
OS Version: Mac OS X 10.11.4 (15E65)
Report Version: 11
Anonymous UUID: D4500160-5025-FCEF-D329-A6A19DF476FA
Sleep/Wake UUID: 6D0875F7-89AC-4308-9F3A-3065723699A7
Time Awake Since Boot: 140000 seconds
Time Since Wake: 3400 seconds
System Integrity Protection: enabled
Crashed Thread: 1 Dispatch queue: OpenGL context pool
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
Assertion failure in +[PAOpenGLDevice _sharedContext], /Library/Caches/com.apple.xbs/Sources/PhotoApp/PhotoApp-370.42/lib/paimaging/Ph otoApps/PAOpenGLDevice.m:220
failed to create shared context: invalid context
abort() called
Thread 0:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff9dcf54e1 objc_msgSend + 33
Xr app for mac. 1 com.apple.AppKit 0x00007fff8edc6f4e +[NSObject(NSKeyValueBindingCreation) _exposedBindings] + 59
2 com.apple.AppKit 0x00007fff8edc6efa +[NSObjectParameterBinder bindingsForObject:] + 42
3 com.apple.AppKit 0x00007fff8edc3496 -[NSObject(NSKeyValueBindingCreation) _binderForBinding:withBinders:createAutoreleasedInstanceIfNotFound:] + 336
4 com.apple.AppKit 0x00007fff8edc35e6 -[NSObject(NSKeyValueBindingCreation) bind:toObject:withKeyPath:options:] + 119
5 com.apple.AppKit 0x00007fff8ed34e98 -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 1041
6 com.apple.AppKit 0x00007fff8ed2be91 loadNib + 384
7 com.apple.AppKit 0x00007fff8ed2b3b7 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:options:withZone:ownerBundle:] + 300
8 com.apple.AppKit 0x00007fff8ed2b180 -[NSBundle(NSNibLoading) loadNibNamed:owner:topLevelObjects:] + 201
9 com.apple.AppKit 0x00007fff8ed2af4c +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 344
10 com.apple.AppKit 0x00007fff8ed261a6 NSApplicationMain + 466
11 libdyld.dylib 0x00007fff922c35ad start + 1
Thread 1 Crashed:: Dispatch queue: OpenGL context pool
0 libsystem_kernel.dylib 0x00007fff8884af06 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff8fa414ec pthread_kill + 90
2 libsystem_c.dylib 0x00007fff96c016e7 abort + 129
3 com.apple.PhotoFoundation 0x0000000111713695 -[PFAssertionPolicyAbort notifyAssertion:] + 58
4 com.apple.PhotoFoundation 0x0000000111712f7e -[PFAssertionPolicyComposite notifyAssertion:] + 223
5 com.apple.PhotoFoundation 0x000000011171317a -[PFAssertionPolicyUnique notifyAssertion:] + 236
6 com.apple.PhotoFoundation 0x000000011171270d -[PFAssertionHandler handleFailureInFunction:file:lineNumber:description:arguments:] + 174
7 com.apple.PhotoFoundation 0x00000001117122f5 _PFAssertFailHandler + 282
8 com.apple.photo.PAImaging 0x0000000111aa8321 +[PAOpenGLDevice _sharedContext] + 108
9 com.apple.photo.PAImaging 0x0000000111aa82ac __31+[PAOpenGLDevice sharedContext]_block_invoke + 21
10 libdispatch.dylib 0x00007fff90d6d40b _dispatch_client_callout + 8
11 libdispatch.dylib 0x00007fff90d6d303 dispatch_once_f + 67
12 com.apple.photo.PAImaging 0x0000000111aa8295 +[PAOpenGLDevice sharedContext] + 98
13 com.apple.photo.PAImaging 0x0000000111aa8031 -[PAOpenGLContext initWithDevice:] + 146
14 com.apple.photo.PAImaging 0x0000000111aa7f85 -[PAOpenGLContextPool _newContext] + 74
15 com.apple.photo.PAImaging 0x0000000111aa7e1e __38-[PAOpenGLContextPool checkOutContext]_block_invoke + 358
16 libdispatch.dylib 0x00007fff90d6d40b _dispatch_client_callout + 8
17 libdispatch.dylib 0x00007fff90d6e9f2 _dispatch_barrier_sync_f_invoke + 74
18 com.apple.photo.PAImaging 0x0000000111aa7c76 -[PAOpenGLContextPool checkOutContext] + 161
19 com.apple.photo.PAImaging 0x0000000111aa7b84 -[PAOpenGLContextPool executeBlockWithContext:] + 52 https://browninfo919.weebly.com/app-iphone-on-mac.html.
20 com.apple.photo.PAImaging 0x0000000111aa7b15 -[PAOpenGLDevice _openGLProperties] + 162
21 com.apple.photo.PAImaging 0x0000000111aa76e7 -[PAOpenGLDevice _deviceProperties] + 123
22 com.apple.photo.PAImaging 0x0000000111aa7460 -[PAOpenGLDevice _lazyInitOnce] + 50
23 com.apple.photo.PAImaging 0x0000000111aa7420 __39-[PAOpenGLDevice _lazyInitOnceIfNeeded]_block_invoke + 41
24 libdispatch.dylib 0x00007fff90d6d40b _dispatch_client_callout + 8
25 libdispatch.dylib 0x00007fff90d6e9f2 _dispatch_barrier_sync_f_invoke + 74
26 com.apple.photo.PAImaging 0x0000000111aa73e6 -[PAOpenGLDevice _lazyInitOnceIfNeeded] + 89
27 libdispatch.dylib 0x00007fff90d7893d _dispatch_call_block_and_release + 12
28 libdispatch.dylib 0x00007fff90d6d40b _dispatch_client_callout + 8
29 libdispatch.dylib 0x00007fff90d7129b _dispatch_root_queue_drain + 1890
30 libdispatch.dylib 0x00007fff90d70b00 _dispatch_worker_thread3 + 91
31 libsystem_pthread.dylib 0x00007fff8fa3e4de _pthread_wqthread + 1129
32 libsystem_pthread.dylib 0x00007fff8fa3c341 start_wqthread + 13
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8884befa kevent_qos + 10
Photos App Crashing Mac High Sierra
1 libdispatch.dylib 0x00007fff90d73165 _dispatch_mgr_invoke + 216
2 libdispatch.dylib 0x00007fff90d72dcd _dispatch_mgr_thread + 52
Thread 3:: Dispatch queue: OpenGL context pool
0 libsystem_kernel.dylib 0x00007fff88844fae semaphore_wait_trap + 10
1 libsystem_platform.dylib 0x00007fff8cb9ace8 _os_semaphore_wait + 16
2 libdispatch.dylib 0x00007fff90d6d3bd dispatch_once_f + 253
3 com.apple.photo.PAImaging 0x0000000111aa8295 +[PAOpenGLDevice sharedContext] + 98
4 com.apple.photo.PAImaging 0x0000000111aa8031 -[PAOpenGLContext initWithDevice:] + 146
5 com.apple.photo.PAImaging 0x0000000111aa7f85 -[PAOpenGLContextPool _newContext] + 74
6 com.apple.photo.PAImaging 0x0000000111aa7e1e __38-[PAOpenGLContextPool checkOutContext]_block_invoke + 358
7 libdispatch.dylib 0x00007fff90d6d40b _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fff90d6e9f2 _dispatch_barrier_sync_f_invoke + 74
9 com.apple.photo.PAImaging 0x0000000111aa7c76 -[PAOpenGLContextPool checkOutContext] + 161
10 com.apple.photo.PAImaging 0x0000000111aa7b84 -[PAOpenGLContextPool executeBlockWithContext:] + 52
11 com.apple.photo.PAImaging 0x0000000111aa7b15 -[PAOpenGLDevice _openGLProperties] + 162
12 com.apple.photo.PAImaging 0x0000000111aa76e7 -[PAOpenGLDevice _deviceProperties] + 123
13 com.apple.photo.PAImaging 0x0000000111aa7460 -[PAOpenGLDevice _lazyInitOnce] + 50
14 com.apple.photo.PAImaging 0x0000000111aa7420 __39-[PAOpenGLDevice _lazyInitOnceIfNeeded]_block_invoke + 41
15 libdispatch.dylib 0x00007fff90d6d40b _dispatch_client_callout + 8
16 libdispatch.dylib 0x00007fff90d6e9f2 _dispatch_barrier_sync_f_invoke + 74
17 com.apple.photo.PAImaging 0x0000000111aa73e6 -[PAOpenGLDevice _lazyInitOnceIfNeeded] + 89
18 libdispatch.dylib 0x00007fff90d7893d _dispatch_call_block_and_release + 12
19 libdispatch.dylib 0x00007fff90d6d40b _dispatch_client_callout + 8
20 libdispatch.dylib 0x00007fff90d7129b _dispatch_root_queue_drain + 1890
21 libdispatch.dylib 0x00007fff90d70b00 _dispatch_worker_thread3 + 91
22 libsystem_pthread.dylib 0x00007fff8fa3e4de _pthread_wqthread + 1129
23 libsystem_pthread.dylib 0x00007fff8fa3c341 start_wqthread + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff8884b5e2 __workq_kernreturn + 10
Update Photos App On Mac
1 libsystem_pthread.dylib 0x00007fff8fa3e578 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff8fa3c341 start_wqthread + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff8884b5e2 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8fa3e578 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff8fa3c341 start_wqthread + 13
Free Photo Apps For Mac
Thread 6:
0 libsystem_kernel.dylib 0x00007fff8884b5e2 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8fa3e578 _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff8fa3c341 start_wqthread + 13
Thread 7:: Dispatch queue: com.apple.root.user-initiated-qos
0 libsystem_kernel.dylib 0x00007fff8884ae8e __psynch_rw_wrlock + 10
1 libsystem_pthread.dylib 0x00007fff8fa3ce1d _pthread_rwlock_lock + 464
2 libobjc.A.dylib 0x00007fff9dd1082c rwlock_tt<false>::write() + 112
Upgrade Photos App On Mac
3 libobjc.A.dylib 0x00007fff9dcfbe70 _class_getNonMetaClass + 33
4 libobjc.A.dylib 0x00007fff9dcfbc88 lookUpImpOrForward + 175
5 libobjc.A.dylib 0x00007fff9dcf5591 objc_msgSend + 209
Photos App On Mac Keeps Crashing
6 com.apple.CoreFoundation 0x00007fff9d420a4d -[__NSArrayM dealloc] + 205
7 com.apple.photo.PAImagingCore 0x0000000111ebb669 +[IPAPhotoEffect initialize] + 1013
8 libobjc.A.dylib 0x00007fff9dcfc390 _class_initialize + 706
9 libobjc.A.dylib 0x00007fff9dcfbc90 lookUpImpOrForward + 183
10 libobjc.A.dylib 0x00007fff9dcf5591 objc_msgSend + 209
11 com.apple.photo.PAImagingCore 0x0000000111ebadb2 +[IPAPhotoEffectOperation initialize] + 573
12 libobjc.A.dylib 0x00007fff9dcfc390 _class_initialize + 706
13 libobjc.A.dylib 0x00007fff9dcfbc90 lookUpImpOrForward + 183
14 libobjc.A.dylib 0x00007fff9dcf5591 objc_msgSend + 209
15 com.apple.photo.PAImaging 0x0000000111aa3b8e __42+[PAImaging _initializeImaging_earlyTasks]_block_invoke_6 + 745
16 com.apple.photo.PAImagingCore 0x0000000111eba0e6 __32-[PALauncher enqueueTask:block:]_block_invoke29 + 50
17 libdispatch.dylib 0x00007fff90d7893d _dispatch_call_block_and_release + 12
18 libdispatch.dylib 0x00007fff90d6d40b _dispatch_client_callout + 8
19 libdispatch.dylib 0x00007fff90d7129b _dispatch_root_queue_drain + 1890
20 libdispatch.dylib 0x00007fff90d70b00 _dispatch_worker_thread3 + 91
21 libsystem_pthread.dylib 0x00007fff8fa3e4de _pthread_wqthread + 1129
Photos App Mac Download
22 libsystem_pthread.dylib 0x00007fff8fa3c341 start_wqthread + 13
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |