Skip navigation
This discussion is archived

Major Aperture 3 memory leak

36140 Views 120 Replies Latest reply: Mar 1, 2010 8:41 PM by vdrummer1 RSS
  • James Stratford Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 12, 2010 1:30 PM (in response to James Stratford)
    Just to follow up,

    I continued to have major performance issues after I turned off Faces although not as bad as before.

    I force quit Aperture and rebooted. After the reboot I started Aperture again. Faces began its work but after a minute or so the page file started ballooning again. I went into Preferences within Aperture and all the pain went away.

    I will come back when my 8k or so images have finished processing and I have turned on Faces again. My hypothesis at this point is perhaps Faces is trying to scan images that are busy being processed rather than restricting itself to fully imported/processed images.

    If this is true it would be a pretty basic bug.
    Mac Mini 2.0GHz Penryn, Mac OS X (10.6.2)
  • Mark Lyon1 Level 1 Level 1 (5 points)
    Currently Being Moderated
    Feb 12, 2010 1:59 PM (in response to Ryan Britton)
    Just to add another puzzled user to the list.

    Simply starting A3 begins to eat real memory. Then virtual memory grows steadily until the dreaded, "Startup disk is full..." error message. Force quitting the program, the only way to stop it, releases resources back to the system. It's unusable. I have imported a dozen images to test out the program before fully committing my library, so lib size should not be an issue.
    iMac 27-in, quad-core i7 8mB, Mac OS X (10.6.2)
  • James Stratford Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 12, 2010 2:20 PM (in response to Mark Lyon1)
    Yeah after a while, even with Faces turned off, I get the memory munching. I got about 20 mins for responsive Aperture then it kicked in.

    Very odd and annoying. I'm just hoping that once I manage to get the library processed it'll run ok from there but it's not great is it?
    Mac Mini 2.0GHz Penryn, Mac OS X (10.6.2)
  • cliverman Calculating status...
    Currently Being Moderated
    Feb 13, 2010 7:32 AM (in response to James Stratford)
    I've experienced the same issues that everyone else has but has anyone actually contacted Apple to see if they acknowledge the problem and are working on a solution?

    Message was edited by: cliverman
    Mac Pro1,1, Mac OS X (10.6.2), 2GB
  • Storn Calculating status...
    Currently Being Moderated
    Feb 13, 2010 8:36 AM (in response to Ryan Britton)
    Apple never acknowledges any problems with their software. I'm experiencing the memory leak as well. Mine starts immediately on executing Aperture. It usually opens up at around 800 megabytes and climbs from there. Not sure why LR3 beta is more stable then A3 final.
    Macbook Pro 15-inc 2.16 C2D, Mac OS X (10.5.1)
  • David Slater Level 6 Level 6 (18,770 points)
    Currently Being Moderated
    Feb 13, 2010 9:58 AM (in response to Ryan Britton)
    why not post in the ADC to Bug Reporter if you think you actually found a bug, work with the developers to fix it
    Quad G5 8.5GB 7800 1TB internal 5TB SATA PM raid Kona LHe, Mac OS X (10.4.11), Rebel XT, 40D
  • Laszlo#13 Calculating status...
    Currently Being Moderated
    Feb 13, 2010 12:56 PM (in response to Ryan Britton)
    Same issue, turned face recognition off, and it still doesn't work. What's also strange, is that I can't run the application in 32 bit. On the Get Info tab, there isn't a tick box to select 32 bit only. The Aperture file is dated Aug. 2009, which is also strange, shouldn't it be newer? In the Get Info tab, it does state version 3. When it runs, it is running in 64 bit. How else can I force it to run in 32 bit? Note that mine was a version upgrade. Are people experiencing the issues with a fresh complete version, or a version upgrade?
    iMac 7,1, Mac OS X (10.6.2)
  • ecarbots Calculating status...
    Currently Being Moderated
    Feb 13, 2010 10:16 PM (in response to Matthew Bergsma)
    Hello, I am a little new to Aperture 3. I love it, but I have noticed my library, with all the photos stored on an external is showing that it is taking up 9GB of space on my computer's drive! I dug into it a little and found that there area ton of "AP.THUMBNAIL" files taking up about 7GB!! Can someone please tell me if A) this is normal, and B) what the difference is between preview files and thumbnails? Do I need these thumbnail files? I realize the previews take up some room, I just don't get why my A3 library was fine, and then all of a sudden it took up 7 more GB.

    macbook pro, Mac OS X (10.6.2)
  • Dan Donovan Level 2 Level 2 (225 points)
    Currently Being Moderated
    Feb 13, 2010 10:35 PM (in response to Ryan Britton)
    Just installed Aperture today and left for the evening while my Library was being converted. Got back and the installation process was frozen with 3% done. A message stated my start-up drive was full. However, my Aperture 2 library and new Aperture 3 Library are on a separate drive. That drive has about 800gb free. I had to force quit. Restarted the computer and my start-up drive has 56gb free space. Something crazy going on.
    Mac Pro: 2.66mhz, 4gb ram, Mac OS X (10.6.2)
  • ecarbots Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 13, 2010 10:40 PM (in response to Dan Donovan)
    Yeah, I can't figure it out! I did notice that I have a thumbnail folder with a bunch of crazy folders and files named AP. THUMBNAIL all over the place taking up 7gb!! I guess I found where the space went, and since my files are backed up I deleted the THUMBNAIL folder to see what would happen and now, of course, the program isn't working to well......please let me know if you have anymore ideas. I know previews and thumbnails generate, but 7GB for thumbnails!! My previews are only 1.5GB.....
    macbook pro, Mac OS X (10.6.2)
  • CalxOddity Level 3 Level 3 (680 points)
    Currently Being Moderated
    Feb 13, 2010 11:11 PM (in response to Dan Donovan)
    I think you'll find that it needs the space on your primary hard disk to use as swap space. Doesn't matter where the library is, it needs the swap space.

    iMac 24" 2.8GHz 4GB RAM, Mac OS X (10.5.8)
  • David G Chapman Level 4 Level 4 (1,390 points)
    Currently Being Moderated
    Feb 14, 2010 2:01 AM (in response to CalxOddity)
    Could somebody report what %age of their HDD was free before starting an upgrade? Once a HDD is 30% full, I/O is slower, at 50% significantly slower and so on. Also useful to know what available memory as reported in Activity Monitor (and Page In/Out's). So, it there is a contention problem between thumbnail and preview builds alongside Faces, it could be exacerbated by the above.
    MBAir 1.8GHz / 8 Core 2.66 4870 12Gb 2.64Tb + Fusion 500P eSATA, Mac OS X (10.6.1), Windows free environment
  • Keith Stead Calculating status...
    Currently Being Moderated
    Feb 14, 2010 2:44 AM (in response to Ryan Britton)
    I've posted this response in another thread, but this thread is probably the more appropriate one: The problem seems to be the updating library routine where the memory requirements to convert an entire library, from version 2 to 3, in one go are excessive. My work around solution was to simply update one month's worth of shots at a time. To do this, I accessed the aperture library folders by using the control key click on the aperture library icon to show the hidden folders and before I dragged all the masters all onto the desk top. I replaced the first one (ie the earliest dated year file) and restarted Aperture. If it locked up, I would replace only one month (from each year) and again restart Aperture (for one month, I had to get down to replacing only one week's file at a time to avoid a lock up). This process reduced the computer's memory load and it worked. Sure it was labour intensive but I had only several thousand photos (not tens of thousands). However, after two hours' work, I now have Aperture 3 running beautifully, fast and without any problems (I'm not that naive to believe there won't be several still to come) but, I'm now happy again.
    iMac, Mac OS X (10.6.2)
  • pberk Level 2 Level 2 (240 points)
    Currently Being Moderated
    Feb 14, 2010 1:24 PM (in response to Ryan Britton)
    I dont think the memory issue has anything to do with upgrading or importing your libraries/photos...

    I started with a new install of Aperture 3 (download version), as I hadn't previously used the program.
    I was able to drag in about 80 photos form iPhoto with no problems... I was able to edit one photo for about 30 minutes before the program totally froze my computer... ON subsequent reboots of the program, I couldn't even get to any editing before the program froze again...

    Today I uninstalled and did a completed new install - the program starts off very snappy (Activity Monitor shows it is using about 250 MB of real memory at that point), but within minutes, without doing anything more than selecting a photo to work on (I was on the phone, not touching the conputer but watching the Activity Monitor), Activity Monitor showed that it progressively ate up 1.66 GB of real memory and almost 3.5 GB of virtual memory and things were totally frozen again... I force quit a few times and rebooted the app and each time it progressively eats RAM until there is nothing left as well as virtual memory....

    This is a severe problem having nothing to do with importing photos or the upgrade version.
    24 iMac intel core 2 duo, Mac OS X (10.6.2), 2 GB RAM
  • pberk Level 2 Level 2 (240 points)
    Currently Being Moderated
    Feb 14, 2010 1:27 PM (in response to pberk)
    Forgot to mention - I have no faces in the photos I imported *they were photos of rooms) - so dont think Faces is the culprit either...
    Mac OS X (10.4.10)
1 2 3 4 ... 9 Previous Next


More Like This

  • Retrieving data ...

Bookmarked By (0)

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.