Skip navigation

Aperture Speed

1626 Views 23 Replies Latest reply: Jan 9, 2012 2:11 PM by léonie RSS
1 2 Previous Next
Longimanus Calculating status...
Currently Being Moderated
Dec 31, 2011 10:21 AM

Hi

 

Can anyone help to help me find out why my Aperture is so slow now, feels like I am back on a PC!

 

I always get the little loading icon up all the time, even when scrolling between photos in split view, it is so annoying, it never used to be like this!

 

In the last couple of days it has started crashing on me, or I have had to force quit it!

 

Is it because of installing lion?  Seemed to be fine before this

IMAC 21"
  • léonie Level 8 Level 8 (46,510 points)
    Currently Being Moderated
    Dec 31, 2011 10:58 AM (in response to Longimanus)

    Tell us please a little bit more about your system: How much RAM do you have, your processor, free space on your hard drive. With Lion you need more RAM than with Snowleopard to run Aperture properly.

     

    And can you post a log from the crash report? The first 50 lines should suffice.

     

    Do you have any plug-ins installed?

  • léonie Level 8 Level 8 (46,510 points)
    Currently Being Moderated
    Dec 31, 2011 12:22 PM (in response to Longimanus)

    If you had any plug-ins you would probably remember installing them. I.e. the Nik plug-ins have been causing crashes on iMacs with Lion. If you have any Aperture plug-ins they would be installed either in

    • your user Library:  /Users/your user name/Library/Application Support/Aperture/Plug-Ins/
    • the system Library: /Library/Application Support/Aperture/Plug-Ins/

    Do you know how to show the hidden Libraries in Lion?

     

    Your free space on the hard drive seems to be sufficient, but the RAM may be a problem. When I upgraded to Lion I had exactly the same situation - Aperture was doing just fine with 4 GB RAM on SL, but on Lion it was continually swapping pages out, because of insufficient RAM.

     

    To check if RAM is the problem, start the Activity Monitor from Applications -> Utilities and click the heading of the column "Real Mem" to sort the processes by memory usage. You will notice, that most of the time Aperture will be at the top of this column, even when doing nothing. Also Safari will be using nearly 1 GB of RAM for its caches and Mail half a GB. If RAM is an issue, it is a good idea to quit these apps when running Aperture.

    When Aperture seems to stall, look at the disk writes. If you get plenty of disk writes in that situation, it would be a sure sign that additional RAM will help.

     

    Did you upgrade to the latest Aperture version 3.2.2?

     

    Regards

    Léonie

     

    P.S. if Aperture crashes again, post the crash log; there have been some problems with Lion and Aperture on iMacs, and a log woud help to narrow down the problem.

     

    activity.png

  • léonie Level 8 Level 8 (46,510 points)
    Currently Being Moderated
    Jan 1, 2012 2:59 AM (in response to Longimanus)

    sorry, I could not get back to you earlier - there was an interruption by Apple maintainance.

    How to post the crash report:

     

    In the Console Window is a left column with Diagnostic and User information. Select the most recent Aperture Crash and then copy the text of the first 50 lines or so to the clipboard and past it into your post. I don't think these lines contain access information to your machine, but we will see the frameworks installed used by Aperture, and that may be helpful.

    crash.png

  • léonie Level 8 Level 8 (46,510 points)
    Currently Being Moderated
    Jan 1, 2012 4:07 AM (in response to Longimanus)

    Hi,

    the part where Aperture crashed is typical for crashes caused by contextual menu items. Where you by any chance right-clicking or ctrl-clicking when the crash occurs? Do you have contextual menues installed, e.g. iView?

    -- Léonie

     

    P.S. I'd remove all traces of Haxies , Application Enhancer, Fruit menu etc., if you have them installed. Dectivating the haxies did bring my Mac back to normal when I switched to Lion.

     

    And since the the program crashed using the com.apple.HIToolbox  Framework, it may help to remove the propertylist /Library/Preferences/com.apple.HIToolbox.plist from the System Library.

  • léonie Level 8 Level 8 (46,510 points)
    Currently Being Moderated
    Jan 1, 2012 4:36 AM (in response to Longimanus)
    what do you mean by iview? or contextual menus.

    That are little helpers that you install that give you menus when you right-click. These menus change, depending on the context you are in, and generally are very useful. But some of those, i.e. the haxies I mentioned above, tweak the system in risky ways, so you have to remember you installed them when you upgrade the system. You find those additional helpers in

    ~/Library/Contextual Menu Items/ or /Library/Contextual Menu Items/ if you have them installed.

    iView is a Photo editor plug-in, that also caused such crashes previously.

     

    The crash report you have, is very typical for a crash caused by these plug-ins. But if you have to ask, what the are, you probaby very wisely refrained from installing those. Otherwise I do not see anything specific in your crash report.

     

    Is it really only Aperture that is crashing? Then I would try if the general basic Troubleshooting measures help; they will be useful if you have a corrupted Aperture Library or faulty preferences.

    Aperture 3: Troubleshooting Basics: http://support.apple.com/kb/HT3805

     

    Also, if you have not done so, run a hardware check to make sure your disk and RAM are o.k.:

    Using Apple Hardware Test: http://support.apple.com/kb/HT1509

  • léonie Level 8 Level 8 (46,510 points)
    Currently Being Moderated
    Jan 1, 2012 10:17 AM (in response to Longimanus)
    I have turned off the photo stream in my icloud settings and it has all seemed to quicken up

    That is a surprising solution, good for you!

     

    Let us know, if this really solved the problem.

     

    Regards

    Léonie

  • SierraDragon Level 4 Level 4 (2,665 points)
    Currently Being Moderated
    Jan 1, 2012 10:57 AM (in response to Longimanus)

    OS versions and app versions usually evolve to use more RAM and system resources as RAM gets cheaper and hardware gets stronger. Basic tech evolution, a good thing. 10.7 typically does require more RAM than 10.6.

     

    Drives slow as they fill so verify that all hard drives are no more than approximately 70% full as a guideline. Even less full is better. Your 500 drive now filled to 380 has been slowing since it was at 200 or so. Your system operation is being slowed by the overfilled internal hard drive.

     

    Even if RAM is not the specific cause of a given anomaly having extra RAM overhead often does seem to facilitate smoother operation. When RAM was expensive designers and users both learned to minimize RAM but with RAM cheap it is illogical to work to minimal RAM amounts.

     

    Add RAM. 4 GB is marginal in 2012 with cheap RAM available.


    You can evaluate whether or not you have adequate RAM by looking at the Page Outs number under System Memory on the Activity Monitor app before starting a typical work session; recheck after working and if the page outs change (manual calculation of ending page outs number minus starting page outs number) is not zero your workflow is RAM-starved. Ignore page ins, the pie charts and other info in Activity Monitor.

     

    If your test shows that page outs increase at all during operation it is affecting performance. You can

     

    • add RAM as feasible

     

    • and/or simply try to run only one app at a time, for sure diligently closing unneeded apps like browsers

     

    • and/or switch 64-bit operation to 32-bit operation (which will make some additional RAM space available). Note that your Mac may already default to 32-bit. See Switching Kernels:

     

    http://support.apple.com/kb/HT3773%5DMac%20OS%20X%20v10.6:%20Starting%20up%20wit h%20the%2032-bit%20or%2064-bit%20kernel

     

    Note that RAM is cheap and heavy apps' usage of more RAM is a good thing.

     

    HTH

     

    -Allen

1 2 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.