-
All replies
-
Helpful answers
-
Jan 13, 2013 11:58 AM in response to CAlan1994by Frank Caggiano,HAve you tried to repair your library? See Aperture 3: Troubleshooting Basics
-
Jan 13, 2013 12:29 PM in response to Frank Caggianoby CAlan1994,Thank You.
Yes, I did. And - after a few crashes Aperture itself detected some inconsistencies and tried to repair the database.
Probably I try to restore a backup and/or to reinstall aperture ...
-
Jan 13, 2013 2:06 PM in response to Frank Caggianoby CAlan1994,Now I have checked all topics of the Troubleshooting Basics - with the result of the same problem.
Do You have any idea to rescue my pictures?
-
Jan 13, 2013 2:47 PM in response to CAlan1994by léonie,★HelpfulAlan,
we need more details:
- What is your Aperture version exactly? Are you using plug-ins with Aperture?
- Are your originals raw or jpeg?
- Where is your Aperture library stored, on an external or internal drive? How is the drive connected?
- What did you do, before the problem first occured? Imported images? Upgraded software? Installed someting new? Moved the library? Run some maintainance application?
- Is other software also behaving funny?
- Is this a recent problem, or did it never work correctly?
A crashlog might help. Can you please post the first sixty lines of the crash report?
And make a few tests please: This will tell us, if your problem is caused by your library, your account, or more general:
- Can you export, if you create a new Aperture library for testing and import a few images into this library?
- If the above test fails, can you export from Aperture, if you log into a different User account and work from this account?
Regards
Léonie
-
Jan 14, 2013 11:53 AM in response to léonieby CAlan1994,Dear Léonie,
thanks for Your patience and indulgence ...
First: I'm calm now, because the library seems to be okay.
I try to response Your questions.
- What is your Aperture version exactly? Are you using plug-ins with Aperture?
- 3.4.3 - no plug-ins
- Are your originals raw or jpeg?
- About 90 percent are jpeg and 100 percent of the problem are jpeg, see below
- Where is your Aperture library stored, on an external or internal drive? How is the drive connected?
- Internal (iMac, Mac Pro or MacBook Pro)
- What did you do, before the problem first occured? Imported images? Upgraded software? Installed someting new? Moved the library? Run some maintainance application?
- I had a lot of pictures to organize, made many new folders and moved many pictures from one project to another. No imports, upgrades, installations, no moving of library. About 15 applications run in background (most with no activity) - but I tested the crashes also without these.
- Is other software also behaving funny?
- No
- Is this a recent problem, or did it never work correctly?
- A recent problem. Since last sunday morning :-)
Tests:
Today I tried to reproduce the crashes on my Mac Pro at the office (and now again on my iMac)
Other libraries don't produce this failure, even the particular library does not - unless I try to export pictures from a definite collection of pictures. If I try to export 1 to a maximum of 24 pictures of these or try to write IPTC-data, all runs well. Above this amount, Aperture crashes no matter which pictures I pick up of these collection of exact 1.862 photos.
If I export hundreds of pictures of another album everything works. I can write IPTC-data to thousands of other pictures.
Only the definite pictures do not work - no matter where they lie. In a project, album, elswhere, even re-imported ... and these pictures don't have many common features. Date, source (scans from different scanners, digitals from different cameras) everything's different - only one is common: the cause of crashes.
It's maddish ... probably a fine feature, which I now try to live with :-)
If You still want to see the crash reports, I can post them.
Best regards and many thanks,
Alan.
-
Jan 14, 2013 12:18 PM in response to CAlan1994by léonie,★HelpfulIf You still want to see the crash reports, I can post them.
Please, the first 50 to 60 lines of one of them - that is really a puzzling problem you are having.
Have the problematic images been externally edited?
-
Jan 14, 2013 2:32 PM in response to léonieby CAlan1994,Yes, many of them especially the scans. And all with Photoshop.
Now I tried to export only not edited pictures from digital cameras. It worked with for example 266 ...
But the many scans I exported from other projects were most edited too.
Only the crazy scans seem to have a problem.
The crash log:
Process: Aperture [1089]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.4.3 (3.4.3)
Build Info: Aperture-310022000000000~2
App Item ID: 408981426
App External ID: 12009533
Code Type: X86-64 (Native)
Parent Process: launchd [256]
User ID: 501
Date/Time: 2013-01-14 19:59:43.634 +0100
OS Version: Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report: 26681 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 3896 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: DEB36F46-AF69-80B6-0569-63CA961A81ED
Crashed Thread: 2
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000ba902ef0
VM Regions Near 0xba902ef0:
-->
__TEXT 000000010a6b5000-000000010ae0b000 [ 7512K] r-x/rwx SM=COW /Applications/Aperture.app/Contents/MacOS/Aperture
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff96ee1686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff96ee0c42 mach_msg + 70
2 com.apple.CoreFoundation 0x00007fff8fa0e803 __CFRunLoopServiceMachPort + 195
3 com.apple.CoreFoundation 0x00007fff8fa13ee6 __CFRunLoopRun + 1078
4 com.apple.CoreFoundation 0x00007fff8fa136b2 CFRunLoopRunSpecific + 290
5 com.apple.HIToolbox 0x00007fff929df0a4 RunCurrentEventLoopInMode + 209
6 com.apple.HIToolbox 0x00007fff929dee42 ReceiveNextEventCommon + 356
7 com.apple.HIToolbox 0x00007fff929decd3 BlockUntilNextEventMatchingListInMode + 62
8 com.apple.AppKit 0x00007fff8ea85613 _DPSNextEvent + 685
9 com.apple.AppKit 0x00007fff8ea84ed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
10 com.apple.Aperture 0x000000010ab2b205 0x10a6b5000 + 4678149
11 com.apple.AppKit 0x00007fff8ea7c283 -[NSApplication run] + 517
12 com.apple.prokit 0x000000010bbda324 NSProApplicationMain + 378
13 com.apple.Aperture 0x000000010a6c54a2 0x10a6b5000 + 66722
14 com.apple.Aperture 0x000000010a6c4df4 0x10a6b5000 + 65012
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff96ee3d16 kevent + 10
1 libdispatch.dylib 0x00007fff98211dea _dispatch_mgr_invoke + 883
2 libdispatch.dylib 0x00007fff982119ee _dispatch_mgr_thread + 54
Thread 2 Crashed:
0 com.apple.CoreFoundation 0x00007fff8fa0ebf9 -[__NSArrayM dealloc] + 185
1 com.apple.CoreFoundation 0x00007fff8f9e785a CFRelease + 170
2 com.apple.CoreFoundation 0x00007fff8f9ebe0a __CFBasicHashDrain + 442
3 com.apple.CoreFoundation 0x00007fff8f9e79af CFRelease + 511
4 com.apple.CoreFoundation 0x00007fff8fb01787 -[__NSDictionaryM dealloc] + 215
5 com.apple.RedRock 0x000000010b134d8a -[RKVersionLRUQueue insert:] + 89
6 com.apple.RedRock 0x000000010b308c36 -[RKVersion(RawSupport) setCGImageProperties:] + 306
7 com.apple.RedRock 0x000000010b106d38 -[RKVersion(RawSupport) cgImagePropertiesWithRaw:] + 620
8 com.apple.RedRock 0x000000010b30c8be -[RKVersion(Imaging) masterSizeForMaster:] + 161
9 com.apple.RedRock 0x000000010b2e60eb -[RKMasterImageRequest initWithVersion:master:size:] + 212
10 com.apple.RedRock 0x000000010b2a854a -[RKVersion(Geode) newMasterImageRequestForMaster:size:useOriginal:description:] + 161
11 com.apple.RedRock 0x000000010b2a849a -[RKVersion(Geode) newMasterImageRequestForMaster:size:useOriginal:] + 82
12 com.apple.RedRock 0x000000010b2bbe2a -[RKImageCache imageForVersion:ofSize:format:colorSpace:description:flags:readyHandler:] + 613
13 com.apple.RedRock 0x000000010b2bba8b -[RKImageCache imageForVersion:ofSize:format:flags:readyHandler:] + 128
14 com.apple.RedRock 0x000000010b2c2c17 -[RKImageCache saveThumbnailsForImportRef:savePreview:] + 1209
15 com.apple.RedRock 0x000000010b15acd2 -[RKImportSavePreviewWorker performJob:forWorkOrder:] + 317
16 com.apple.proxtcore 0x000000010c8e164a -[XTWorker performJob:] + 111
17 com.apple.proxtcore 0x000000010c8abb16 -[XTDistributor distributeMessage:] + 444
18 com.apple.proxtcore 0x000000010c8ab4d9 -[XTThread handleMessage:] + 342
19 com.apple.proxtcore 0x000000010c8aa292 -[XTThread run:] + 345
20 com.apple.Foundation 0x00007fff98580612 __NSThread__main__ + 1345
21 libsystem_c.dylib 0x00007fff94f64742 _pthread_start + 327
22 libsystem_c.dylib 0x00007fff94f51181 thread_start + 13
-
Jan 14, 2013 3:35 PM in response to CAlan1994by léonie,Such a kind of crash looks like a data error - corrupted image file. Aperture crashes, when it is freeing memory (-[__NSArrayM dealloc] ) - that should on no account happen.
One thing is funny - you are saying, the problematic files are all jpegs, but the code looks to me, like Aperture were using code from the raw support:
6 com.apple.RedRock 0x000000010b308c36 -[RKVersion(RawSupport) setCGImageProperties:] + 306
7 com.apple.RedRock 0x000000010b106d38 -[RKVersion(RawSupport) cgImagePropertiesWithRaw:] + 620
8 com.apple.RedRock 0x000000010b30c8be -[RKVersion(Imaging) masterSizeForMaster:] + 161
Are you sure, that your selection does not contain raw files, maybe stacked?
And if Aperture cannot export the original files - have you checked, if you can edit the files, that you selected for export? For this, Aperture needs to access the original files too. I'd try to add dummy adjustments to a set of images, for that Aperture crashes on export. You can revert the adjustments immediately after trying to apply them. This is just to test, if Aperture can work with the originals.
-
Jan 15, 2013 1:14 PM in response to léonieby CAlan1994,I don't use stacks yet.
Yes, I saw the entry RawSupport too. But when I filter the project to data type, there's no raw.
Additionally these photos were all taken in 2003+2004 and at this time I had no camera with raw capability.
Editing is possible. I tried to edit about 40 pictures and it works. Opening with PS and saving ...
-
Jan 15, 2013 2:05 PM in response to CAlan1994by léonie,Editing is possible. I tried to edit about 40 pictures and it works. Opening with PS and saving ...
And using Aperture's adjustments to edit the images? Sharpening, brushes? Is that possible?
You are saying the images are scans - jpegs. If the images have been edited with PS as an external editor they wíll no longer be jpeg, they will have new quasimasters - tiff or psd files. How is your external editor set? Are you returning layered PSDs? How large are your scans? Can it be that the scans (converted to tiff or psd) are too large for Aperture? How much RAM do you have?
You said you looked at trouble shooting measures, that Frank Caggiano pointed to?
Aperture 3: Troubleshooting Basics
Have you tried any of them, besides the library repair/rebuild?
I hope Frank will have some more good ideas
-
Jan 15, 2013 4:05 PM in response to léonieby CAlan1994,I'm very sorry, I never used the (great) possibilities of Aperture before - now I used some with these weird photos. Very handy and it works well. Even with my pictures ;-)
But my workflow is very different. I use (and love) Aperture to organize my photos for business and private use.
Up til now, the pictures have been imported after finishing (with PS) as jpegs. The most of them (for business) don't need any editing, because they are only for documentation.
The problematic photos are all private and not so big (only from our house building and some more ...). The biggest one, a scan from dia, has 5.3mb.
The iMac (9,1) has 8GB, the Mac Pro 12GB.
I have checked all topics of the troubleshooting basics. Inclusive restore a recent direct backup from external drive, a restore from a time capsule backup, replacing plists and application support data, re-install of Aperture (App Store version).
It's a little painful for me, that You insist on solving my little "problem" - although I can understand this and thank You again for Your effort.
By the way: today I have exported all the 1.862 pictures with the help of Keyboard Maestro. Little packages of 10 per export :-)
Works fine although this is no lasting solution ...
But now comes something completely different:
I just wanted to send this post, but before I had a look at the problematic photos, picked one and selected "Info". Aperture crashed. See the log below. The next time the crash does not occur :-(
It was one of the scans of dias. Is it possible to send You one or two of these extraordinary scans? Or helps a link to dropbox?
Process: Aperture [1765]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.4.3 (3.4.3)
Build Info: Aperture-310022000000000~2
App Item ID: 408981426
App External ID: 12009533
Code Type: X86-64 (Native)
Parent Process: launchd [277]
User ID: 501
Date/Time: 2013-01-16 00:53:10.885 +0100
OS Version: Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report: 77673 sec
Crashes Since Last Report: 4
Per-App Interval Since Last Report: 28274 sec
Per-App Crashes Since Last Report: 3
Anonymous UUID: DEB36F46-AF69-80B6-0569-63CA961A81ED
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
*** error for object 0xf26cc300: pointer being freed was not allocated
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8cbb1212 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff8ac33af4 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff8ac77dce abort + 143
3 libsystem_c.dylib 0x00007fff8ac4b959 free + 392
4 com.apple.CoreFoundation 0x00007fff856dcc75 -[__NSArrayM dealloc] + 309
5 com.apple.Aperture 0x000000010bfc4322 0x10be58000 + 1491746
6 com.apple.CoreFoundation 0x00007fff856b585a CFRelease + 170
7 com.apple.CoreFoundation 0x00007fff856f349c -[__NSArrayI dealloc] + 140
8 libobjc.A.dylib 0x00007fff8ad88230 (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 464
9 com.apple.CoreFoundation 0x00007fff856dd342 _CFAutoreleasePoolPop + 34
10 com.apple.Foundation 0x00007fff8e2134fa -[NSAutoreleasePool drain] + 154
11 com.apple.AppKit 0x00007fff8474a35e -[NSApplication run] + 736
12 com.apple.prokit 0x000000010d37d324 NSProApplicationMain + 378
13 com.apple.Aperture 0x000000010be684a2 0x10be58000 + 66722
14 com.apple.Aperture 0x000000010be67df4 0x10be58000 + 65012
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8cbb1d16 kevent + 10
1 libdispatch.dylib 0x00007fff8dedfdea _dispatch_mgr_invoke + 883
2 libdispatch.dylib 0x00007fff8dedf9ee _dispatch_mgr_thread + 54
Thread 2:
0 libsystem_kernel.dylib 0x00007fff8cbb10fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8ac36fc3 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff8e279933 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff8e279789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.proxtcore 0x000000010e05403a -[XTMsgQueue waitForMessage] + 47
5 com.apple.proxtcore 0x000000010e053282 -[XTThread run:] + 329
6 com.apple.Foundation 0x00007fff8e24e612 __NSThread__main__ + 1345
7 libsystem_c.dylib 0x00007fff8ac32742 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff8ac1f181 thread_start + 13