Im a heavy Aperture user, just about everyday on it. I have a dedicated 27” iMac late 2012 with 16gb ram, graphics 680GX w 2GB. Dedicated meaning I run AP and PS on it only, well..Photomatrix Pro and Silver effects pro. I recently had the Main Board replaced 2mos ago due to a failed graphics card.
Today I had a crash while AP was opened and I was doing simple Key-wording. Activity Monitor stated Crash in Thread 0, does that mean a machine or an App problem.
Called my Apple reseller / repair people and they said an Application crash of 1/month is kinda normal for a non repeatable crash/problem.
Question: How often should or does your Apperture just quit on you???
Question: How often should or does your Apperture just quit on you???
I can’t remember the last time Aperture has outright crashed. Sure, an occasional slowdown or maybe a random spinning beach ball … but I can’t ever recall a flat out crash or kernel panic under routine use. There was a version a year or so back that caused some issues right out of the box when it updated … but a trash and delete of all app and preference files, then re-install made it all better.
I am running a 2011 21.5” with 12GB RAM with i5 2.5 Ghz and AMD Radeon HD 6750M 512 MB graphics card … hardly cutting edge in the line.
I routinely have Aperture, Photoshop, FCP X, Motion 5, Safari, Mail and Transmit all running at the same time. I sometimes see a slowdown in app switching waiting for RAM to swap out … but no crashes.
I do think there are lemon models/machines. I have an older MBP (2006 Core 2 Duo, 2.4 Ghz. 4GB RAM that I use as backup for road work … that particular unit was trouble from the start … seems it received one of the faulty NVIDIA graphics card and had all kinds of heat and fan issues … it wash’t until Apple replaced the video card, mother board, HD, power exchanger that it ran efficiently without overheating (all under warranty) … since I popped in an SSD … it works rather well.
This sounds more like a hardware issue - perhaps bad RAM (had that happen once). Run a hardware diagnostics and see what comes up.
David:
My aperture, latest edition, on an older machine than yours without the same power –rarely crashes. That is, just plain crashes. Rarely.
Best.
Thanks all!! Guess I need to make an appointment at the Genius Bar and not the Guinness Bar. Cheers
davidbmoore@mac.com
Twitter= @davidbmoore
Scottsdale AZ
David,
Not sure I fully get it. Are you worry after only 1 crash?
I will say that I get crashes every 2 months roughly. Enough that I remember but not enough to make me worry :)
J.
I have not had a crash on either of my iMacs (24 and 21.5) with the exception of a RAM failure causing a kernel panic. Aperture, however, did crash one time in the last two years and that was just recently…have no clue why but it has not happened since. Thank goodness!
Joe Im worried caused Ive had the graphics card replaced and still getting crashes. I don’t think they designed it to do that. Almost all crashes are in the thread 0 which I think means is not Aperture but Aperture put a load on the machine to cause it to hiccup .
Going to genius bar today.. its up to them now to say its a problem they want to fix.
davidbmoore@mac.com
Twitter= @davidbmoore
Scottsdale AZ
Apple genius thinks I have software issues and since its a Pro App referred me back to the Apple care guys. Crashed yesterday while doing Aperture n PS together. Here is the notice from the console if any knows what it means please let me know
Date/Time: 2014-05-03 15:34:03.769 -0700
OS Version: Mac OS X 10.9.2 (13C1021)
Report Version: 11
Anonymous UUID: 28A8ACB6-D4F7-C356-7E3C-A10497016471
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
*** Terminating app due to uncaught exception ‘NSUnknownKeyException’, reason: ‘[<RKWebSourceItem 0x608000666180> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key arrangedFilteredChildren.’
terminating with uncaught exception of type NSException
abort() called
davidbmoore@mac.com
Twitter= @davidbmoore
Scottsdale AZ
This is definitely an Aperture bug. Report it to Apple and provide them the full crash report. You can get that from the Applications > Utilities > Console application. You can see from the screenshot below where I found a “Crash Report” from Aperture dated May 2, 2014.
Photographer | https://www.walterrowe.com | https://instagram.com/walter.rowe.photo