Aperture hanging and until force quit

Tony,

Thanks again.

xtravoice,

thanks for the information...

Same here! Aperture was working great until a few days ago and now after three adjustments there goes the ball! I was wondering if anyone from Apple is looking into this a a software problem if so many people are experiencing the same issue. I have followed advice on how to fix it and still nothing. Also I really doubt it is a corrupt file due to the fact it does it on just about every file I have attempted to work on and they are not all in the same project. Help I am getting really aggravated at this!
Thanks

So, I decided to update to 3.0.3 from version 2.1.4 a couple days ago. Library all processed, all the repair, rebuilds done that are suggested.

Works great! For about 6 adjustments! Then hang! Spinning beach ball and then nothing.

Seems Aperture 3.0.3 is pretty worthless so far. Wish I wouldn't have "upgraded". Not sure there is a way to downgrade though....

Stay away from Aperture 3 until it gets fixed properly!!!!

Are those getting the beachball after a few edits running in full-screen mode? If so, can you reproduce the problem doing those same edits in a Viewer window?

-Steve

I had been having the same problem, only my beach ball would start without me doing any adjustments- then I would have to force quit. Now, EVERY TIME I restart Aperture, I rebuild the database. It runs fine until I close it. If I restart, w/o rebuilding the database, I get the beach ball. I let Aperture run in the background all the time, and haven't had any problem. This doesn't fix the orginal problem; just a workaround for me so that I can get work done.

In my case I eventually found the hanging to be caused by a corrupt keyword, one that has endlessly copied itself internally. The problem is that this keyword is not visible accessible in the Keywords HUD, and so cannot be removed. My fear is of course that remediation will destroy the keywords list. I do not want to have to re-key the 95GB worth of photographs.
I am assuming that an export:edit txt file:re-import routine will not remove the rogue keyword because the rogue is not visible therein.
Generally the keywords list seems a bit flakey, with odd things occurring from time to time.

What is a "rogue" or "corrupt" keyword, and how did you find it? Something containing illegal characters? And rebuilding your database didn't fix it?

You might be able to use [exiftool http://www.sno.phy.queensu.ca/~phil/exiftool/ to diagnose or repair the problem if the keyword has been applied to master files. I don't know how Aperture-applied keywords are stored in Aperture's database.

-Steve

I'll second (or third, or whatever the number is by now) the thought that Aperture 3.0.3 is not Apple quality software.

I very recently decided to try Aperture again (having tried 3.0 when it first came out - and finding it close to useless). Since then I upgraded to a new Macbook Pro with 8GB of RAM; and Apple upgraded Aperture to v3.0.3.

I use iPhoto a lot - and it works quite well with my 100,000+ image library. I just wish it had a better editor with more capable corrections for color, red-eye etc.

Aperture imported this library - and processed for a couple of days, during which I just let it run.

After everything had settled down, I started making some minor color hue adjustments to some pictures.

It hung with the beach ball and "not responding" after the 6th or so adjustment. This was within 15 minutes of me starting to use the app for real - having waited a couple of days to finish "processing". That's very disappointing.

Frankly I'm not very interested in rebuilding libraries or other tricks - particularly having just freshly installed and imported my iPhoto library.

If this is supposed to be the "pro" version of iPhoto then it fails miserably. iPhoto is far more stable, faster, and generally more usable.

I had waited for 3.0.3 and a new Mac before trying it a second time - but this time I think I have to wait for v4.

I hope Apple gets it right - I like the company and most of their software. This product just seems to lag behind on the quality front.

I have just posted this on the Feedback page for Aperture:

Where to begin. You guys must be reading the forums. This upgrade is bringing pros & amateurs alike to our knees. Just one example: I have wasted a whole morning - May I bill you for my half-day at £250? - No? I thought not.....The task: print out 250 images as 7 x 36 shot contact sheets. Result - NADA - ZILCH - NOT A SAUSAGE. Aperture at numerous tries took up to 35 minutes to reach the point when the preprint process crashed. Eventually I used Aperture to create 250 50% jpegs sent to the desktop. This task took 17 minutes. Not exactly 'speed of light'. I then dropped this folder into Adobe Bridge and created my contact sheets. This took a couple of minutes and the contacts printed perfectly within a couple more minutes. So not much wrong with the rest of my set-up. I am getting so many problems that I do not believe this release is fit-for-purpose.

Aperture 3 is one huge mess of features and a box of trouble. My fellow pros who use Lightroom are having hysterics at our expense and believe me it is costing us money.

I am experiencing the same problem. Aperture freezes after one edits a few pictures. I have tried the fixes in Apples article, rebuild database, reinstall Aperture & it still hangs up the program. Now I will regenerate all previews and thumbnails and not turn of Aperture, lets see if that helps..!

Have any of you tried running on 32 bit version of instead? Some info in the forums that it might be more stable that way.

on the 32 bit version, well for me it did not work, still get the beach ball especially with "straighten" command.