ie11

Q: Why is aperture crashing on my brand new 27" iMac ?

I just purchased a new 27" imac:

 

Model Name:          iMac

  Model Identifier:          iMac14,2

  Processor Name:          Intel Core i7

  Processor Speed:          3.5 GHz

  Number of Processors:          1

  Total Number of Cores:          4

  L2 Cache (per Core):          256 KB

  L3 Cache:          8 MB

  Memory:          16 GB

 

I purchased this to replace my 2008 MBP whish was too slow for editing large files.  I saved up to buy this new machine and am at wit's end already.

 

I installed Aperture (original disc and upgrade disc, then did upgrade to latest version via ap store.

I imported files from one SD card (less than 900 files) into Aperture. They are on my drive, not an external. I have not even set up time

 

I have opened iphoto and opened photostream for that, but not for Aperture.

 

I have not installed any plugins for Aperture--though I own Photomatix and am waiting to install it until this is resolved.

 

I did not transfer anything from my previous machine, nor use migration assistant as I wanted this to be very clean. I've only set up two email addresses in mail--seriously I'm keeping this machine clean.

 

SO...My first Aperture session resulted in a spontaneous re-boot.  Since then, Aperture has crashed (and I've sent a report) each of the 4 or 5 times I've tried to use it. I'm doing basic things like cropping, viewing with and without the loupe, rotating through view between thumbnails, full screen and

 

What gives?!

 

THE WHOLE REASON I SPENT THIS MUCH MONEY IS TO USE APERTURE TO EDIT PHOTOS.

iMac, OS X Mavericks (10.9.1)

Posted on Jan 6, 2014 1:06 PM

Close

Q: Why is aperture crashing on my brand new 27" iMac ?

  • All replies
  • Helpful answers

Previous Page 2
  • by ie11,

    ie11 ie11 Jan 8, 2014 6:19 PM in response to chris5s
    Level 1 (10 points)
    Jan 8, 2014 6:19 PM in response to chris5s

    Interesting.  We'll hope for the best and keep meeting back here.

     

    Did you try the library repair? DId it work? Hellp for a while?

     

    DId you try anything else?

     

    My prior is also a 2008 MBP (early though) with 8GB. Snap!

  • by chris5s,

    chris5s chris5s Jan 9, 2014 8:26 AM in response to ie11
    Level 1 (55 points)
    Jan 9, 2014 8:26 AM in response to ie11

    I'm sorry to tell you that repairing the library did not help. What usually helps is working on some images, then quitting and restarting aperture.

  • by Jon Roemer,

    Jon Roemer Jon Roemer Feb 19, 2014 2:13 PM in response to chris5s
    Level 2 (225 points)
    Feb 19, 2014 2:13 PM in response to chris5s

    I am seeing the exact same crash on a brand new Retina Macbook Pro (10.9.1, Aperture 3.5.1)

     

    Problem occurs if I try to use the loupe:

     

    Crashed Thread:  0  Dispatch queue: com.apple.main-thread


    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

    Exception Codes: EXC_I386_GPFLT


    Application Specific Information:

    objc_msgSend() selector name: isKindOfClass:



    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

    0   libobjc.A.dylib                         0x00007fff83ad9097 objc_msgSend + 23

    1   com.apple.CoreImage                     0x00007fff8382e6e1 -[CIFilter setValue:forKey:] + 76

    2   com.apple.Aperture                      0x000000010c894400 0x10c69b000 + 2069504

    3   com.apple.AppKit                        0x00007fff8ba69399 -[NSView _drawRect:clip:] + 3748

    4   com.apple.AppKit                        0x00007fff8ba67c0e -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1799

    5   com.apple.AppKit                        0x00007fff8ba67fea -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2787

  • by chris5s,

    chris5s chris5s Feb 19, 2014 2:31 PM in response to Jon Roemer
    Level 1 (55 points)
    Feb 19, 2014 2:31 PM in response to Jon Roemer

    Sorry to hear that, although I am glad that apparently not only iMacs seem to be affected. This should keep the pressure on Apple to get this fixed.

     

    I'm hoping 10.9.2 will be the cure...

     

    Chris

  • by chris5s,

    chris5s chris5s Feb 26, 2014 9:08 AM in response to chris5s
    Level 1 (55 points)
    Feb 26, 2014 9:08 AM in response to chris5s

    It seems that 10.9.2 fixed this bug. I haven't seen a crash in AP after installing the update yesterday and mem usage in Activity Monitor suggests that Aperture (or the graphics driver) no longer exhibit a memory leak.

    Chris

  • by Red Rock Rick,

    Red Rock Rick Red Rock Rick Mar 19, 2014 9:13 AM in response to ie11
    Level 1 (4 points)
    Safari
    Mar 19, 2014 9:13 AM in response to ie11

    I have read this thread. 

     

    The program Aperture is where the problem lies.  It has a bug. There may be some issues with 10.0.2 also but Aperture 3.5.1 is still not fixed.  I think the Aperture logs are recording everything you do when processing a picture.  This is causing a memory overload.  What is happening for me is that the free memory is slowly being depleted until the lack of free memory causes a crash or the "wheel of death".

     

    My system

    Mac Pro - 6-core Intel Processor 3.33 GHz

    OS - 10.9.2

    Memory - 20 GB

    Hard Drive - 500 GB SSD

    Graphics Card - ATI Radeon HD 5870 1024MB

     

    Ever since I upgraded Aperture shortly after installing Mavericks - I have had a memory problem with Aperture. I use Aperture professionally and process raw images.  I CAN'T go through a learning curve on a new program. 

     

    Here is how I have adjusted to the problem of memory overload or memory pressure to avoid crashes.  Hopefully, Apple will fix the problem for all of us.

     

    1. Utilize 3 different apps to stay on top of the system eating memory. Keep Activity Monitor open in background

     

    2. Free App in Mac App store - called Free Memory - You set it up in activity bar and monitor your memory usage.  Set up an alarm to free the memory.  I use 1 Gig left as an alarm

     

    3. I upgraded the free app for $1.99. It is called Memory Diag.app - It also frees the memory.  As the memory gets critical I click on the app and it works to free memory. 

     

    4. As I work on a particular picture and apply different brushes such as Burn Effect - I sometimes just close down Aperture and re-open it.  Apparently this eliminates the log and the memory pressure goes back to normal. According to the IT person I use, this indicates that the problem is with Aperture and not the operating system.

     

    5. One more area that I checked out from previous threads.  For some reason, if you start Quicktime and start a full screen recording, the memory does not deplete as quickly.  It worked for me - until it didn't!  By that I mean, I left it running too long and the computer crashed.  It only works for short periods of time.  I would only do a screen recording for less that 5 minutes.

     

    If it is the OS then the memory pressure woiuld not change if you quit Aperture until you shut down the computer and restart it.

     

    Hope this helps keep you from going down the wrong rabbit hole on this problem. 

     

    Nothing seems to fix it.  Reinstalling the Mavericks and Aperture will not help.  The problem will come back.  Aperture needs the correct update to fix this problem.  Generally, new computers with factory installed OS will work fine with all programs that have not gone through updates and were designed for that operating system. This seems to be a redesign problem with the updated Aperture.

  • by stevenfrommesa,

    stevenfrommesa stevenfrommesa Apr 13, 2014 9:10 PM in response to Red Rock Rick
    Level 1 (0 points)
    Apr 13, 2014 9:10 PM in response to Red Rock Rick

    I'm having the same problem as well on a fully loaded iMac 27". Mine is even worse however as all my user files are on a a drobo. So each time, I have to do a time machine restore to get the computer to remember where all my user files are. I called apple and they just did a repair permissions and that hasn't made any difference. Looking forward to a permanent fix.

Previous Page 2