Q: as soon as I launch Aperture 3.6 within 1 minute it crashes with the "ProviderImageSurfaceCacheQueue"
-
Apr 19, 2016 7:40 PMby LarryHN,Nope - Photos is a totally new and different program that has nothing in common with Aperture - Most of the PHotos code is in the OS where as APerture is pretty much a stand alone application
The APertue forum may be able to help but the photos for will not be able to - I will request that your post be put in the proper place
and reply with details including the OS version you are using and the first 100 or so lines of the crash log
and of course since the OP noted the solution you may want to try it although since you have a totally different problem with totally different software the odds are not great
LN
-
Apr 19, 2016 9:33 PMby DSwanMN,Duh, sorry, I see my post was already moved to the Aperture forum. It is really odd how this suddenly went south. Was working fine, no new software installed, Aperture working fine, then crashed, and now never makes in more than 1 minute before crashing. Aperture library is 343GB, so have avoiding to a full DB rebuild (versus repair).
I have also uninstalled Aperture and Reinstalled. Same issue.
How can I be sure where the source of the issues is (Aperture bits, OS bits, or the library itself)? Is it possible to hide/rename my current library and see if aperture will work with a new/fresh library?
As for the crash details here they are. System info at the end:
==
Process: Aperture [713]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.6 (3.6)
Build Info: Aperture-500021000000000~3
App Item ID: 408981426
App External ID: 731142774
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Aperture [713]
User ID: 501
Date/Time: 2016-04-19 23:25:24.888 -0500
OS Version: Mac OS X 10.11.4 (15E65)
Report Version: 11
Anonymous UUID: 8DF2754A-2B87-7707-352B-6FE7498F9D50
Time Awake Since Boot: 1300 seconds
System Integrity Protection: enabled
Crashed Thread: 15 Dispatch queue: ProviderImageSurfaceCacheQueue
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000134703000
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0x134703000:
MALLOC_LARGE 00000001343d0000-0000000134703000 [ 3276K] rw-/rwx SM=PRV
-->
JS JIT generated code 0000578caa200000-0000578caa201000 [ 4K] ---/rwx SM=NUL
==
Here is my system summary:
Model: MacBookPro6,1, BootROM MBP61.0057.B11, 2 processors, Intel Core i7, 2.66 GHz, 8 GB, SMC 1.57f18
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E4D3136464B44
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E4D3136464B44
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.100.24)
Bluetooth: Version 4.4.4f4 17685, 3 services, 27 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Samsung SSD 850 PRO 1TB, 1.02 TB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: IR Receiver
USB Device: Built-in iSight
Thunderbolt Bus:
-
Apr 19, 2016 9:54 PMby léonie,Crashed Thread: 14 Dispatch queue: ProviderImageSurfaceCacheQueue
Can you post the messages from this thread? Scroll down in the crash log and post the lines from thread 14. Then we can see what this thread was trying to do when it crashed.
When you are launching Aperture, open the Activity window from the View menu. It will display the images and videos, Aperture is trying to process.
Does Aperture launch without crashing, if you are holding down the options key while launching Aperture?
-
Apr 19, 2016 9:58 PMby DSwanMN,Sure, but I will get a fresh crash dump for you and the corresponding details from whatever thread crashed (as I don't have the original dump). New dump and details below. I appreciate the help!
Crashed Thread: 3 Dispatch queue: ProviderImageSurfaceCacheQueue
Thread 3 Crashed:: Dispatch queue: ProviderImageSurfaceCacheQueue
0 libsystem_platform.dylib 0x00007fff99d9962d _platform_memmove$VARIANT$Nehalem + 205
1 com.apple.CoreImage 0x00007fff9995312a ___ZNK2CI12ProviderNode7surfaceERK6CGRect_block_invoke_10 + 55
2 com.apple.CoreImage 0x00007fff999cf036 SurfaceApplyPlaneBlock + 164
3 com.apple.CoreImage 0x00007fff999530cd ___ZNK2CI12ProviderNode7surfaceERK6CGRect_block_invoke_9 + 468
4 com.apple.CoreImage 0x00007fff999e2e28 ___ZN2CI17SurfaceCacheEntry9fillAsyncEv_block_invoke + 30
5 libdispatch.dylib 0x00007fff9a46493d _dispatch_call_block_and_release + 12
6 libdispatch.dylib 0x00007fff9a45940b _dispatch_client_callout + 8
7 libdispatch.dylib 0x00007fff9a45e03b _dispatch_queue_drain + 754
8 libdispatch.dylib 0x00007fff9a464707 _dispatch_queue_invoke + 549
9 libdispatch.dylib 0x00007fff9a45cd53 _dispatch_root_queue_drain + 538
10 libdispatch.dylib 0x00007fff9a45cb00 _dispatch_worker_thread3 + 91
11 libsystem_pthread.dylib 0x00007fff963f64de _pthread_wqthread + 1129
12 libsystem_pthread.dylib 0x00007fff963f4341 start_wqthread + 13
-
Apr 19, 2016 10:27 PMby léonie,It looks like a serious program error on the system level; a segmentation fault (SIGSEGV). You get this error, when a program is referencing array entries out of bounds of the range of the array or possibly running out of memory.
Corrupted data in caches, currupted images can also be causing such error messages.
The backtrace is showing a call to the "Coreimage" framework, so my bet is that you might have an unreadable image somewhere or a library corruption.
Test with a new, empty Aperture library to exclude caches and preferences files as the possible reason of these crashes. Launch Aperture while holding down the options key to get to the Library Chooser panel. Then create a new, empty library. can Aperture work with new imported image files?
- If Aperture cannot work with a new library, restart the Mac in Safe mode to clear caches. See: Mac OS X: Starting up in Safe Mode
Then remove Aperture's cached containers - the complete folder:
~/Library/Containers/com.apple.Aperture/
Boot again normally and try again.
- If Aperture can work with a new library, do these tests:
When you are launching Aperture, open the Activity window from the View menu. It will display the images and videos, Aperture is trying to process.
Does Aperture launch without crashing, if you are holding down the options key while launching Aperture?
-
Apr 19, 2016 11:13 PMby léonie,If the crash is because of the Preview generation, Aperture should work, if you launch it while holding down the Shift key. The Shift key prevents Aperture from rendering previews during that session.
- Try to launch Aperture this way and then delete the file 2015-10-02 TRWildGame 3.
- Empty the Aperture Trash and recover the deleted item from the Trash bin on your Desktop and test it in another application.
-
Apr 19, 2016 11:31 PMby DSwanMN,You are a life saver!
That worked!
I opened with Shift (no previews) and no crash. I then simply clicked on that file to view and that also crashed Aperture. I again reopened with no previews and this time accessed the file from the contextual menu and deleted it (moved to aperture trash) and emptied trash to system trash.
At this point, I opened Aperture in regular mode, Activity showed preview generating correctly and all activity tasks completed.
Following your suggestion, I tried opening that jpg file in preview and it worked fine, so I am not sure exactly what is/was wrong with it, but I am able to move on with a good Aperture library.
Now that it is working, do you suggest I do a library repair one last time?
Thanks again so much!
