wbs_
Level 1 (0 points)

Q: memory leak

I am using an iMac 27 with 16 GB memory.

 

Working on my RAW pictures Aperture 3.5.1 is "eating" step by step this memory and in the end when a few MB is left - Aperture crashes (after 2 hours working).

 

Is anybody out there observing the same behavier?

Aperture 3, OS X Mavericks (10.9.1)

Posted on Jan 21, 2014 12:59 AM

Close
wbs_

Q: memory leak

  • All replies
  • Helpful answers

Page 1 Next

  • by Phl At Home,

    Phl At Home Phl At Home Jan 21, 2014 3:22 AM in response to wbs_
    Level 1 (0 points)
    Jan 21, 2014 3:22 AM in response to wbs_

    Yes I have the same problem using Aperture but just using JPEG images.

     

    I also have a imac 27 but with 8GB, Aperture 3.5.1 plus Mavericks 10.9.1.

  • by wbs_,

    wbs_ wbs_ Jan 21, 2014 3:31 AM in response to wbs_
    Level 1 (0 points)
    Jan 21, 2014 3:31 AM in response to wbs_

    I discovered this problem already about 2 yeras ago. But with a product update it had disappeard.

    But now the problem is back!

     

    Does Apple know about it? At least I am sending an error report to Apple every crash ...

  • by léonie,

    léonie léonie Jan 21, 2014 6:04 AM in response to wbs_
    Level 10 (107,610 points)
    iCloud
    Jan 21, 2014 6:04 AM in response to wbs_

    On my iMac and MBP 17" it isn't Aperture, that is eating the memory, but Safari and Mail. Do you have any of these applications running in the background?

    I am seeing these crashes, even if only Mail and Safari are running; I do not need to run Aperture 3.5.1 to make the Mac hang or crash. The process that keeps crashing is "mdworker", it is using more than 1 GB memory. And this did not change, even after a clean install of the system with only the Apple provided system applications plus Aperture 3.5.1 and the new Mavericks versions of iLife, iWork, and Final Cut X installed and rebuilding the Spotlight index for good measure.

  • by Najinsky,

    Najinsky Najinsky Jan 21, 2014 6:16 AM in response to wbs_
    Level 3 (670 points)
    Jan 21, 2014 6:16 AM in response to wbs_

    Yes, Apple are aware of it, but keep sending reports, just so they don't forget.

     

    If dificult to say with certainty where the true problem lies (Aperture or Mavericks) but for me, turning of 'On Screen Proofing' in Aperture resovles the issue (I submitted bug feedback to Apple and they contacted me for additional info and suggested I try turning 'On Screen Proofing' off). So I know Apple is aware of it, and for me the problem was only manifesting in Aperture, and with OSP on.

     

    Andy

  • by wbs_,

    wbs_ wbs_ Jan 21, 2014 6:32 AM in response to léonie
    Level 1 (0 points)
    Jan 21, 2014 6:32 AM in response to léonie

    I am sure, it's Aperture. I am running an App called "Mistat" showing me the amount of memory Aperture is using, and I can watch it growing until no memory is left (just before the crash).

  • by wbs_,

    wbs_ wbs_ Jan 21, 2014 6:34 AM in response to Najinsky
    Level 1 (0 points)
    Jan 21, 2014 6:34 AM in response to Najinsky

    Thank you for your input. Could you please give an hint where I find the 'On Screen Proofing'. I am using a German Version and can not find something that matches to that.

  • by Najinsky,

    Najinsky Najinsky Jan 21, 2014 6:45 AM in response to wbs_
    Level 3 (670 points)
    Jan 21, 2014 6:45 AM in response to wbs_

    Screen Shot 2014-01-21 at 21.36.02.jpg

     

    Also, regarding the memory usage, for sure Aperture is the one consuming memory, but that doesn't automatically make it an Aperture bug, for example, Aperture could be coded appropriately to release memory but something in Mavericks could be stopping that memory from actually being released. What Léonie is saying is she has observed the same behaviour in other Apps, while not using Aperture, adding evidence it may be a more general bug.

     

    Andy

  • by wbs_,

    wbs_ wbs_ Jan 21, 2014 7:11 AM in response to Najinsky
    Level 1 (0 points)
    Jan 21, 2014 7:11 AM in response to Najinsky

    OK, I found it. Thanks a lot.

    By the way, in German language it is called "Auf dem Bildschirm überprüfen" (whatever happens here).

     

    I switched it off - let's see what happens.

  • by léonie,

    léonie léonie Jan 21, 2014 7:20 AM in response to wbs_
    Level 10 (107,610 points)
    iCloud
    Jan 21, 2014 7:20 AM in response to wbs_

    Are you sure, that MiStat is compatible with Mavericks? I looked at Roaring Apps ( http://archive.roaringapps.com/app:204 ) and it is only listed as compatible with MacOS X 10.6 to 10.8.

     

    You can check the memory usage also with the system provided "Activity Viewer" in your "Programme > Dienstproramme" folder.

  • by wbs_,

    wbs_ wbs_ Jan 21, 2014 7:33 AM in response to léonie
    Level 1 (0 points)
    Jan 21, 2014 7:33 AM in response to léonie

    Yes, I kow Activity Viewer. Mistat is showing the exact same numbers as Activity Viewer.

     

    But, here is what I just found in Activity Viewer (in RED):   "QTKitServer-(11484) Aperture (reagiert nicht)"

  • by léonie,

    léonie léonie Jan 21, 2014 7:49 AM in response to wbs_
    Level 10 (107,610 points)
    iCloud
    Jan 21, 2014 7:49 AM in response to wbs_

    Yes, I kow Activity Viewer.

    My concern is, that MiStat could be causing the problems, if it is not compatible. I'd test with only Aperture running and no third-party applications at all, and after rebooting the mac.

     

    "QTKitServer-(11484) Aperture (reagiert nicht)"

    That error message has been reported in many threads recently, in connection with many different apps in Mavericks (iPhoto, Safari, Motion, Aperture). I have not seen a clear solution for this, however.

  • by chris5s,

    chris5s chris5s Jan 21, 2014 9:32 AM in response to léonie
    Level 1 (55 points)
    Jan 21, 2014 9:32 AM in response to léonie

    I am seeing these crashes with AP 3.5.1, 10.9.1 on a late 2013 iMac i7 as well. It does not matter, wether I have on screen proofing switched on or off. What I observe in Activity Viewer is that the used memory gets used up while editing pictures or browsing in non fast-preview (Schnelle Vorschau), but Aperture's displayed mem usage does not go up by the same amount. As soon as physical memory is used up, Aperture starts to crash. I have seen the "QTKitServer() Aperture(reagiert nicht)" message as well, but Aperture crashes even if that stuck process is not listed in Activity Viewer.

     

    There are several threads revolving around this very same issue (e.g. https://discussions.apple.com/message/24407575), so I would suggest we don't get sidetracked by assuming that some third party software causes these crashes, but rather keep sending crash reports to Apple.

  • by wbs_,

    wbs_ wbs_ Jan 21, 2014 9:45 AM in response to chris5s
    Level 1 (0 points)
    Jan 21, 2014 9:45 AM in response to chris5s

    Right you are!

    In my case Aperture crashes as discribed even if all other Apps are not started, means: no Mistat, no Safari, no Mail, no Motion, no iPhoto, etc.

     

    And I also suppose that it is not Mavericks, because the exact problem I had about 2 years ago with Aperture under Lion.

  • by Frank Caggiano,

    Frank Caggiano Frank Caggiano Jan 21, 2014 9:55 AM in response to wbs_
    Level 7 (25,796 points)
    Jan 21, 2014 9:55 AM in response to wbs_

    Has anyone tried running in Safe Mode? Aperture use to refuse to start in safe mode but I believe that with Mavericks and 3.5.1 it will run. Would be interesting to see if it makes any difference.

     

    Also there is this small App EtreCheck written by a frequent contributor to ASC that will report on the state of the system. The data output can be useful in troubleshooting problems like this one.

Page 1 Next