You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: nycnftm
nycnftm Author
User level: Level 1
8 points

Photos In High Sierra Kees Crahing

Photos crashes daily. I tried a bunch of things and still having issues.


I tried

  • reset PRAM
  • Check disk disk first aid
  • rebuild photos library
  • create new photos library


Somebody must have the answer


Computer specs:

  • High Sierra 10.13.6
  • Photos 3.0
  • Mac Mini (2011)
  • Memory 8 GB 1333 mhz ddr3


Part of crash log. Not sure if you want to see ALL of it.


Process: Photos [3632]

Path: /Applications/Photos.app/Contents/MacOS/Photos

Identifier: Photos

Version: 3.0 (3291.13.230)

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Photos [3632]

User ID: 501


Date/Time: 2020-09-05 02:14:00.749 -0400

OS Version: Mac OS X 10.13.6 (17G12034)

Report Version: 12

Anonymous UUID: 0F76C200-C581-E786-11E4-C42B959F1D16



Time Awake Since Boot: 27000 seconds


System Integrity Protection: enabled


Crashed Thread: 0 Dispatch queue: com.apple.main-thread


Exception Type: EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes: 0x0000000000000001, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY


Termination Signal: Illegal instruction: 4

Termination Reason: Namespace SIGNAL, Code 0x4

Terminating Process: exc handler [0]


Application Specific Information:

Crashing on exception: *** -[__NSPlaceholderArray initWithObjects:count:]: attempt to insert nil object from objects[0]


Application Specific Backtrace 1:

0 CoreFoundation 0x00007fff2ed6a0db __exceptionPreprocess + 171

1 libobjc.A.dylib 0x00007fff560ab942 objc_exception_throw + 48

2 CoreFoundation 0x00007fff2edaa16c _CFThrowFormattedException + 194

3 CoreFoundation 0x00007fff2ec6a3bd -[__NSPlaceholderArray initWithObjects:count:] + 237

4 CoreFoundation 0x00007fff2ec714b4 +[NSArray arrayWithObjects:count:] + 52

5 Photos 0x000000010636f110 +[IPXAvailableAssetManager preloadVersions:excludeAudio:] + 1445

6 Photos 0x000000010636eb47 +[IPXAvailableAssetManager preloadVersions:] + 67

7 Photos 0x000000010601c799 -[IPXAvailableAssetManager submit:] + 177

8 Photos 0x0000000105f8b24d -[PFAction(IPXAction_Extensions) executeAndRegisterWithUndoManager:] + 552

9 Photos 0x00000001061838bf __133-[IPXRenderChangeAction showExternalEditAlertIfNeededForExternalEditController:inWindow:onContinueExecuteAndRegisterWithUndoManager:]_block_invoke + 51

10 Photos 0x000000010653639c -[IPXExternalEditSessionController showExternalEditAlertIfNeededForVersions:inWindow:completion:] + 392

11 Photos 0x000000010618384e -[IPXRenderChangeAction showExternalEditAlertIfNeededForExternalEditController:inWindow:onContinueExecuteAndRegisterWithUndoManager:] + 200

12 Photos 0x00000001063e636d -[IPXViewerImageController _rotateBy:] + 295

13 Photos 0x0000000106387ff8 -[IPXEditorController a_rotateLeft:] + 79

14 AppKit 0x00007fff2ca09a43 -[NSApplication(NSResponder) sendAction:to:from:] + 312

15 AppKit 0x00007fff2c49e213 -[NSMenuItem _corePerformAction] + 323

16 AppKit 0x00007fff2c49df9b -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 114

17 AppKit 0x00007fff2c49cdff -[NSMenu performKeyEquivalent:] + 363

18 AppKit 0x00007fff2ca086a9 routeKeyEquivalent + 884

19 AppKit 0x00007fff2ca05ce0 -[NSApplication(NSEvent) sendEvent:] + 1096

20 AppKit 0x00007fff2c26687d -[NSApplication run] + 812

21 AppKit 0x00007fff2c235a3a NSApplicationMain + 804

22 libdyld.dylib 0x00007fff56cc6015 start + 1


Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.apple.AppKit 0x00007fff2c59c454 -[NSApplication _crashOnException:] + 109

1 com.apple.AppKit 0x00007fff2c59c33c -[NSApplication reportException:] + 953

2 com.apple.AppKit 0x00007fff2c26690e -[NSApplication run] + 957

3 com.apple.AppKit 0x00007fff2c235a3a NSApplicationMain + 804

4 libdyld.dylib 0x00007fff56cc6015 start + 1


Mac mini, macOS 10.13

Posted on Sep 4, 2020 11:28 PM

Reply
Question marked as Top-ranking reply
User profile for user: léonie
léonie
User level: Level 10
197,189 points

Posted on Sep 5, 2020 12:46 AM

Reinstalling from Recovery will not erase the user data, just replace the system by a fresh copy. Photos is a part of the system, and mainly a wrapper for calls to system services, so you can only reinstall it by reinstalling the system.


When you test Photos, be sure to launch by clicking the copy in the Applications folder and not the Dock icon or an alias on the Desktop. These may be linked to older versions of Photos from a previous system version.


When you tested with a new Photos Library, did you test with a new photo, that has not yet been edited? The backtrace in the crash log is indicating, that Photos has been working with an externally edited photo. Have you been working with an external editor, when the crash happens or is Photos crashing right during the start-up? If the crash happens during an external editor session, you may need to update the external editor.


To reinstall Photos from Recovery, follow the instructions in this document: How to reinstall macOS from macOS Recovery - Apple Support


Reinstalling the current system from Recovery with ⌘R is easy and relatively quick, but it will only help if the problem is system wide and not caused by a problem in your own user account. Have you already tested by launching Photos in a different user account with basic preferences settings, for example in the Guest user account? Reinstalling will only help, if you are seeing the same problem in a different, fresh user account: How to test an issue in another user account… - Apple Community



View in context

Similar questions

9 replies
Question marked as Top-ranking reply
User profile for user: léonie
léonie
User level: Level 10
197,189 points

Sep 5, 2020 12:46 AM in response to nycnftm

Reinstalling from Recovery will not erase the user data, just replace the system by a fresh copy. Photos is a part of the system, and mainly a wrapper for calls to system services, so you can only reinstall it by reinstalling the system.


When you test Photos, be sure to launch by clicking the copy in the Applications folder and not the Dock icon or an alias on the Desktop. These may be linked to older versions of Photos from a previous system version.


When you tested with a new Photos Library, did you test with a new photo, that has not yet been edited? The backtrace in the crash log is indicating, that Photos has been working with an externally edited photo. Have you been working with an external editor, when the crash happens or is Photos crashing right during the start-up? If the crash happens during an external editor session, you may need to update the external editor.


To reinstall Photos from Recovery, follow the instructions in this document: How to reinstall macOS from macOS Recovery - Apple Support


Reinstalling the current system from Recovery with ⌘R is easy and relatively quick, but it will only help if the problem is system wide and not caused by a problem in your own user account. Have you already tested by launching Photos in a different user account with basic preferences settings, for example in the Guest user account? Reinstalling will only help, if you are seeing the same problem in a different, fresh user account: How to test an issue in another user account… - Apple Community



Reply
User profile for user: léonie
léonie
User level: Level 10
197,189 points

Sep 5, 2020 1:23 AM in response to nycnftm

How to create a new Photos Library and to switch between libraries is described here in the Photos User Guide: Create additional photo libraries in Photos on Mac - Apple Support


  1. If Photos is open, choose Photos > Quit Photos.
  2. Hold down the Option key and double-click the Photos icon in the Applications folder (or click the Photos icon in the Dock) to open Photos.
  3. In the Choose Library dialog, click Create New.
  4. Type a library name and choose a location to store the library.
  5. Click OK.


The Photos Library needs to be in folder, that is supported by Photos. The best place would be the Pictures folder in your user account. Do not put it on your Desktop or in the Documents folder, if iCloud is syncing the Desktop and Documents folder to iCloud. If you are keeping your Photos Libraries on an external volume, the volume must not have been used for Time Machine backups or accessed over the network. The file system format needs to be MacOS Extended (journaled) and not case-sensitive. Move your Photos library to save space on your Mac - Apple Support


Reply
User profile for user: rcosta887
rcosta887
User level: Level 4
3,604 points

Sep 4, 2020 11:38 PM in response to nycnftm

If it's happening even with a brand new Photos Library like you tried, then it's something with macOS itself. The easiest thing to try would be installing the macOS High Sierra 10.13.6 combo update which re-applies all of the existing High Sierra updates in one shot, and would hopefully fix any corrupted files as I'm pretty sure one of the updates did include a Photos App update at some point.

https://support.apple.com/kb/DL1970?locale=en_US


If that doesn't work you could rip out the Photos App itself and then do a refresh overtop reinstall of High Sierra on top of itself from recovery (Command R on boot up) mode.

Reply
User profile for user: léonie
léonie
User level: Level 10
197,189 points

Sep 5, 2020 2:02 AM in response to nycnftm

The test with the new library is telling you, if there is a problem with your main library. The library might be damaged, or in an unsupported location, or contain corrupted videos or photos. If Photos is not crashing on a new library, you know, that the old library has a problem. The new library will not automatically show the photos.


The photos will have to be moved from the old library to the new library. Does Photos crash on your old library directly, when you launch Photos, or are you able to export photos from the old library?



Reply
User profile for user: nycnftm
nycnftm Author
User level: Level 1
8 points

Sep 9, 2020 4:19 AM in response to nycnftm

Spoke too soon. Imported pics from iPhone and just crashed with new library. Do I paste the girnt log here or is there a better way?


Process: Photos [5358]

Path: /Applications/Photos.app/Contents/MacOS/Photos

Identifier: Photos

Version: 3.0 (3291.13.230)

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Photos [5358]

User ID: 501


Date/Time: 2020-09-09 07:05:44.215 -0400

OS Version: Mac OS X 10.13.6 (17G12034)

Report Version: 12

Anonymous UUID: 0F76C200-C581-E786-11E4-C42B959F1D16


Sleep/Wake UUID: 6E0A63C8-BBB4-4242-B23D-7B481F2A1D54


Time Awake Since Boot: 50000 seconds

Time Since Wake: 13000 seconds


System Integrity Protection: enabled


Crashed Thread: 0 Dispatch queue: com.apple.main-thread


Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000024513673bec8

Exception Note: EXC_CORPSE_NOTIFY


Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [0]


Reply

Photos In High Sierra Kees Crahing

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up