aToast

Q: Aperture 3.3 update & now all I get is the spinning beach ball

Aperture worked fine all this time...until I updated to 3.3

 

Now after Aperture is launched, without me having to do ANYTHING in Aperturit goes to the spinning beach ball and says "Processing" at the bottom of the window.

And I can't do anything except Force Quit.

 

In the course of Troubleshooting, I've done the following...

 

Held down the OPTION and COMMAND keys while launching Aperture in order to:

Repair Permissions

Repair Database

Rebuild Database

 

Restarted the iMac (multiple times)

 

Used Disk Utility to Repair Disk Permissions

 

Anybody have insights into how to get Aperture 3.3 to work?

 

Thanks.

iMac, Mac OS X (10.7.4)

Posted on Jun 28, 2012 3:49 PM

Close

Q: Aperture 3.3 update & now all I get is the spinning beach ball

  • All replies
  • Helpful answers

Page 1 Next
  • by shuttersp33d,

    shuttersp33d shuttersp33d Jun 28, 2012 4:36 PM in response to aToast
    Level 4 (1,540 points)
    Jun 28, 2012 4:36 PM in response to aToast

    You should try downloading 3.3.1 (released today), and then go through a repair as you did before, holding the option and command keys while launching.

  • by aToast,

    aToast aToast Jun 28, 2012 6:31 PM in response to shuttersp33d
    Level 1 (75 points)
    Jun 28, 2012 6:31 PM in response to shuttersp33d

    Thanks for the advice!  I wasn't aware of the 3.3.1 update.  Unfortunately, it didn't help at all.

     

    Once again in 3.3.1, I tried the following...

     

    Held down the OPTION and COMMAND keys while launching Aperture in order to:

    Repair Permissions

    Repair Database

    Rebuild Database

     

    Restarted the iMac

     

    Used Disk Utility to Repair Disk Permissions

     

    But still, I get the same exact problem: after Aperture launches, without me having to do ANYTHING in Aperture, it goes to the spinning beach ball and says "Processing..." at the bottom of the window.  And all I can do is Force Quit.

     

    My Aperture Library is really not that big, I don't have any referenced photos, and it was working just fine before the update to 3.3.

     

    Any ideas? 

  • by Kirby Krieger,Helpful

    Kirby Krieger Kirby Krieger Jun 28, 2012 6:39 PM in response to aToast
    Level 6 (12,522 points)
    Jun 28, 2012 6:39 PM in response to aToast

    aToast wrote:

     

    Any ideas? 

    Stop force-quitting?

     

    Aperture is trying to fix whatever it has found needs to be fixed in your Library.  Force-quitting almost always makes databases less robust.

     

    How long have it you let it run?  Have you been able to open the Activity window?  What did it report?

     

    Did you really install 3.3.1 and go through each of "Repair Permissions", "Repair Database", and "Rebuild Database"?  I'm not sure the upgrade has been out long enough to have done all that.

     

    Message was edited by: Kirby Krieger

  • by aToast,

    aToast aToast Jun 28, 2012 7:25 PM in response to Kirby Krieger
    Level 1 (75 points)
    Jun 28, 2012 7:25 PM in response to Kirby Krieger

    Thanks for the insights!

     

    I really have a pretty small Aperture library.  It's only 2.5 GB.  (Most of my pics are in iPhoto)

    ...I'm guessing that's why the Repair Permissions, Repair Database and Rebuild Database took such a short time.

     

    Thanks for the tip on checking the Activity Window!

    It's saying it's "Synchronizing MobileMe Gallery," which now has a status of "Completing"

     

    I'm gonna just let Aperture spin its beach ball and see what happens.

     

    Thanks again for the suggestions!

     

    I'll report back...

  • by Kirby Krieger,Helpful

    Kirby Krieger Kirby Krieger Jun 28, 2012 7:43 PM in response to aToast
    Level 6 (12,522 points)
    Jun 28, 2012 7:43 PM in response to aToast

    Do you have a MobileMe gallery?

     

    If so ... let it run.

     

    I ask because there have been some phantom connections being made to Photostream and to Facebook since the 3.3 upgrade.

  • by aToast,

    aToast aToast Jun 28, 2012 8:09 PM in response to Kirby Krieger
    Level 1 (75 points)
    Jun 28, 2012 8:09 PM in response to Kirby Krieger

    Kirby, thanks so much for the advice!

     

    Yes, I had/have MobileMe Galleries.  Again, not a lot, though.  More like experiments than actual galleries I cared about, which is why I didn't bother taking them down manually before the June 30 MobileMe end date.  No Facebook albums.

     

    I am letting Aperture continue playing with the beach ball...

     

    Activity Window seems to have moved on from MobileMe.  I think and hope that's a good sign.

    It's doing Faces now: "Face detection" with "28 Remaining"

  • by Kirby Krieger,

    Kirby Krieger Kirby Krieger Jun 28, 2012 8:20 PM in response to aToast
    Level 6 (12,522 points)
    Jun 28, 2012 8:20 PM in response to aToast

    aToast wrote:

     

    I am letting Aperture continue playing with the beach ball...

     

    Activity Window seems to have moved on from MobileMe.  I think and hope that's a good sign.

    it is  .  After it's all done, go to "Aperture➞Preferences➞Web➞Accounts" and delete the MobileMe account if you no longer use it.  This will delete all MobileMe Albums in Aperture (your Originals and any Versions will not be deleted, nor -- afaik -- will any of the albums that show on Mobileme), and may prevent some cruft from clogging things up later on.

  • by ebenabbaan,

    ebenabbaan ebenabbaan Jun 28, 2012 8:47 PM in response to Kirby Krieger
    Level 1 (0 points)
    Jun 28, 2012 8:47 PM in response to Kirby Krieger

    Having the same problem; ironically, my main Aperture library on my mac pro (315GB) updated easily; it's the tiny 'annex' library I keep on my Laptop that continues with the beach ball.

     

    Unfortunately I cannot get to the activity window (due to the app being frozen) but I'll wait it out and see what happens and report back...

  • by Kirby Krieger,

    Kirby Krieger Kirby Krieger Jun 28, 2012 8:57 PM in response to ebenabbaan
    Level 6 (12,522 points)
    Jun 28, 2012 8:57 PM in response to ebenabbaan

    5 of 6 Libraries I use/oversee upgraded seamlessly.  Unfornately for me, the one that didn't gagged horribly and is so large it's going to take dozens of hours of processing just to see if it's usable.  More than a bit of a cockup on Apple's part, imho.

  • by aToast,

    aToast aToast Jun 29, 2012 6:42 AM in response to Kirby Krieger
    Level 1 (75 points)
    Jun 29, 2012 6:42 AM in response to Kirby Krieger

    I left Aperture to spin its beach ball overnight.  When I returned this morning, it was still still spinning, in the same place I saw it when I went to bed.  Aperture's Activity window showed the same thing as last night I let it go for a few minutes to make sure the iMac wasn't still just waking up or something.

     

    I can also report that in my iMac's Activity Monitor, it showed the following (in case it helps shed light on the problem):

    Aperture (not responding)

    100% of CPU

    45 Threads

    822.1 MB Real Mem

     

    ...I'm getting ready to call AppleCare this morning...

     

    of course, any insights are welcome!  I haven't posted often in these discussion forums and I'm pleasantly surprised at how helpful it's been.  Thanks you guys!

  • by ebenabbaan,

    ebenabbaan ebenabbaan Jun 29, 2012 6:56 AM in response to aToast
    Level 1 (0 points)
    Jun 29, 2012 6:56 AM in response to aToast

    Had the same problem.  I'm going to copy the library in question to my other computer (a Mac Pro, which successfully upgraded its very large Aperture library) and see what happens.  Maybe it can fix/repair my MacBook Pro's small Aperture library, then I can copy it back over and everything will be swell.

     

    (And if this works maybe I can set up a little 'fix-you-aperture-library' freelance business)

  • by léonie,

    léonie léonie Jun 29, 2012 7:02 AM in response to ebenabbaan
    Level 10 (108,869 points)
    iCloud
    Jun 29, 2012 7:02 AM in response to ebenabbaan

    -

  • by ebenabbaan,

    ebenabbaan ebenabbaan Jun 29, 2012 7:16 AM in response to léonie
    Level 1 (0 points)
    Jun 29, 2012 7:16 AM in response to léonie

    Yes, obviously I upgraded to 3.3.1 before upgrading anything.

     

    But yeah, the Mac Pro 'processed' my files (the Activity Window showed that it was generating thumbnails).  When it was done I copied the library back onto my Laptop, deleted the old one, and it runs fine.  Sorry this isn't really helpful though...

  • by aToast,Solvedanswer

    aToast aToast Jun 30, 2012 8:13 AM in response to aToast
    Level 1 (75 points)
    Jun 30, 2012 8:13 AM in response to aToast

    OK, so I didn't have time to call AppleCare and decided not to after all.

     

    I solved it by:

    - using Time Machine to restore my Aperture Library from the time before I upgraded Aperture

    - right-clicked on the now-restored Aperture Library and launched it using iPhoto

    - iPhoto ran through Processing and Upgrades and reported it couldn't find a movie file, etc.

    - I couldn't find the movie file iPhoto was referring to but did all I could to 'clean up' the files in iPhoto

    - I then quit iPhoto and launched the Aperture Library using Aperture...

    ...and it worked.

    There was still a little cleaning up to do (I did use Preferences in both iPhoto and Aperture to delete the connection to my MobileMe Galleries/iCloud account).

    Then relaunched Aperture again to make sure it's still working, clicked on random photos to make sure I wasn't just seeing thumbnails.

     

    Everything seems to be there and okay.

     

    Good luck everyone!!!

     

    C'mon Apple!

Page 1 Next