Currently Being ModeratedAug 19, 2011 7:53 AM (in response to ringhome)
You're right you shouldn't have to work around this and nothing you do in the program should cause it to crash.
Take a look at the Aperture 3: Troubleshooting Basics there are a few other things you can try besides what you've already done. Specifically I try moving the preferences's file out to see if that makes a difference.
Also I'd try creating a new empty library, import a few images and try what crashes Aperture in that library. Finally you can try making a new user and running Aperture as that user to se if it makes a difference.
Report your results, good luck
Currently Being ModeratedAug 19, 2011 8:48 AM (in response to ringhome)
This is in the Keywords HUD?
Voodoo, fwiw: Create a new Keyword, we'll call it "Focus Two". Expand "Focus" by way of your work-around. Select all the sub-items of "Focus". Drag and drop them onto "Focus Two". Delete "Focus". Does the disclosure triange for "Focus Two" work? If so, close Aperture, re-open, and try again.
If not, you might drag Keywords one at time until you find the Keyword (or the number of Keywords) that trips the system.
Agreeing with Frank, this is abnormal and improper.
Currently Being ModeratedAug 19, 2011 9:13 PM (in response to Kirby Krieger)
I did try all of this with the same results: crash. It didn't matter what the size. It did help narrow down the choices.
Currently Being ModeratedAug 19, 2011 9:14 PM (in response to Frank Caggiano)
I ended up trashing the Preferences file and all was well.
Currently Being ModeratedAug 19, 2011 9:23 PM (in response to ringhome)
Glad you got it sorted -- and very helpful to know what actually worked. Thanks for posting your results.
Currently Being ModeratedAug 19, 2011 10:35 PM (in response to Kirby Krieger)
You're not going to believe this, but it's back. It worked initially, which is why I gave it a thumbs-up. Then I went and put some of the preferences back. Go to use the keywords and BAM!
I decided for scientific purposes to try the removable of the preferences again. Now not even that works.
I will see if rebuilding helps, then I'll try a smaller library (it is about 17K images).
Thanks for the help. I'm still open for ideas.
Currently Being ModeratedAug 20, 2011 3:18 PM (in response to Kirby Krieger)
Well, this time I got it to work for sure. I really didn't want to do it, but I had to. When I tried a smaller library and keywords there then all was well. I think my problem was related to either the defrag I did, which had Time Machine start up (I forgot to disable it when I cloned). Who knows what else, but something corrupted a key (no pun intended) part of the database.
My solution (draconian?) was to just make a new library. Yep, for 14.7K images. It took a while, but all seems well.
Thanks for the input.
Currently Being ModeratedAug 20, 2011 7:18 PM (in response to ringhome)
Thanks for the update. Best wishes -- I hope you don't find the same problem in the new Library.
I, too, have always resisted the brute-force approach -- as though my computer "feels" work in some way similar to me. This projection is all too human, and of course silly.
At the end of last week I relocated a very large Masters set (~500 GB, many of them small files) to a new drive. I thought this would take my computer about 24 hr. to finish. It took about 54. No problems at all. (Fwiw, I'm now convinced that it is faster to copy very large Masters sets via Finder and then use "Locate Referenced Files" than it is to "Relocate Masters". Not a surprise.)
Currently Being ModeratedAug 22, 2011 7:39 AM (in response to ringhome)
Glad to see you finally fonud a solution for your problem.
One question I have concerns your statement
I think my problem was related to either the defrag
What defrag operation were you doig that may have lead to your problem?
Just curious, regardsiMac Intel 3.06 GHz 8GB Mem; Macbook5.1 2.4ghz 4GB Mem, Mac OS X (10.6.8), Aperture 3.1.3
Currently Being ModeratedAug 22, 2011 4:28 PM (in response to Frank Caggiano)
To begin with, the problem is back. To answer your question, I had booted from my clone and was doing a defrag with Disk Warrior.
I guess I look pretty silly claiming victory twice. My grad school advisor once said he was putting me on the 24-hour rule (no responses until I thought about it 24 hours). All seemed well for a while and now it doesn't work.
I can't believe a mere 14.7K images should kill it. What the heck could that do? In any case, I tried making another library with about 7K images with no problem.
It would seem that this is very unusual, seeing as I can't find anyone else that's had this problem.
In any case, I've put in a bug report with Apple. I can use a flat list, if I have to.
Thanks for the help.
Currently Being ModeratedAug 22, 2011 6:12 PM (in response to Frank Caggiano)
I guess that I failed to do the last (or next to last) set of remedial action in the Aperture 3 Troubleshooting Guide: Reinstall (per instructions, I might add). It seems to be okay, even after a restart. If it dies again, well, I think I'll go crawl in a hole.
Currently Being ModeratedFeb 3, 2012 1:19 PM (in response to ringhome)
I'm probbaly a little late to this thread, but let me add my experience anyway in case it helps somebody.
Background: just downloaded and installed Aperture 3 trial on a fairly new & clean MacBook Air. I hope to evaluate Aperture as a replacement to ACDSee Pro 3, which I've used to organise and edit roughly 180k images spanning 15 years. Changing my main workflow tool with a library that size is a bit daunting to say the least ...
The first thing I did was to import a folder of 2.5k images from Kenya into Aperture to mess around with. I noted that the list of standard keywords that Aperture trial ships with was now joined by 'Safari', which had over 400 images associated with it. I'd assigned this keyword liberally in ACDSee and embedded it in the JPG metadata along with many other keywords, but these weren't showing up in Aperture.
On trying to expand the standard list of keywords Aperture crashed, leading me to this forum post and the workaround of adding a temporay keyword to get the lists to expand. In this way I was able to junk some the standard keywords. I renamed 'Safar' to 'Kenya Safari', and after that I was able to expand and contract the other lists too.
My guess is that Aperture wasn't able to parse some character(s) it found in the JPG metadata when importing my images, resulting in only 'Safari' being registered in the keywords list. Whatever else was imported interfered with the expansion of the list, and renaming the keyword stripped out the offending character, causing the list to function again.
I know this is a long shot but I can sort of see it working. If you're still having issues with your keywords, maybe try renaming those that were created through import and not natively in Aperture?