10 Replies Latest reply: Nov 11, 2013 12:43 PM by léonie
saba01 Level 2 Level 2 (320 points)

Hi,

I am working with Aperture since the beginning and never had any issue. I did work on 17 MBP and pulled now the plug on a maxed out 15 rMBP (16 GB, 1TB). I have transferred the library from my 17 to the retina. Now when I work in a project (usually around 1200 pictures JPEG 16 MP) Aperture or better the whole computer crashes after working for 15 to 20 min just sorting out pictures and deleting the ones not needed. The computer just becomes unresponsive and freezes so it has to be restarted. Before it happens I get usually a memory warning 3 to 4 times. I never had something like that in the past 7 or so years working with Aperture. Any Idea? It is almost impossible to work now professional with the Retina; so any help is highly appreciated .

  • 1. Re: Aperture crashes on rMBP, I need help
    Ernie Stamper Level 8 Level 8 (37,475 points)

    My rMBP runs circles around my old Mac Pro with Aperture, so do not understand what may be your problem.

     

    What version of Aperture and OSX, btw, and how did you install Aperture?  Directly or by migration from the old MBP?

     

    Ernie

  • 2. Re: Aperture crashes on rMBP, I need help
    saba01 Level 2 Level 2 (320 points)

    I did migrate first, but have reinstalled and run Mavericks a course (came with the rMBP). Yes, it is fast.... until it stalls, I somehow have the feeling that the 1TB SSD is too fast, so Aperture chokes??

  • 3. Re: Aperture crashes on rMBP, I need help
    Ernie Stamper Level 8 Level 8 (37,475 points)

    I doubt that conclusion as cause.  I believe a Repair of the Library might be in order.

     

    Ernie

  • 4. Re: Aperture crashes on rMBP, I need help
    saba01 Level 2 Level 2 (320 points)

    Repair of library was my first idea, so I did that :-( 

    And I found something strange, perhaps someone here has an idea what it means. I get in the status bar the used and free memory displayed in real time always. That works fine since years.... it works fine with every program now - except Aperture. I have 16 GB memory when I start Aperture used and free memory adds up to 16 GB, BUT the longer I work in Aperture the less the total sum of memory becomes, so before it comes to a stall I have something like used: 7980 free: 323 what would be 8302 (where are my other 7697 ???????) this strange thing only happens in Aperture and only when I work quite a while. And yes, I did test the memory, it is ok.

  • 5. Re: Aperture crashes on rMBP, I need help
    léonie Level 9 Level 9 (51,720 points)
    until it stalls, I somehow have the feeling that the 1TB SSD is too fast, so Aperture chokes??

     

    Aperture 3.5 is working well for me on the internal SSD (MBP) with 16 GB RAM. But it would not hurt to run a File System Check on your System drive with Disk Utility . Select the system partition in the sidebar of Disk Utility and run "Verify Disk". Is all o.k.? (Don't run "Repair Permissions" from Disk Utility on a drive with an Aperture Library).

     

     

    Now when I work in a project (usually around 1200 pictures JPEG 16 MP) Aperture or better the whole computer crashes after working for 15 to 20 min just sorting out pictures and deleting the ones not needed. The computer just becomes unresponsive and freezes so it has to be restarted.

     

    Just to be clear - the title of your question says "Aperture crashes", but now you are saying "Aperture is unresponsive". Does Aperture actually crash with an error message and crash report, or is it just hanging?

    Repair of library was my first idea, so I did that :-(

    Have you repaired permissions or repaired the database, or both?  After migrating the library to a new user account, "Repair permissions" id necessary. And after each force quit a "Repair database" is necessary strongly recommended.

     

    How did you move your Aperture library over? Copy using the Finder, migrate with Migration Assistant?

     

    Your Aperture library may contain files, that are not readable or cannot be processed by Aperture.  While you are working with Aperture, do you have the "Activity Window" open (View > Show Activity). Do you see any activities in that window, when Aperture is starting to hang?

     

    Do you see any error messages in the Console Window?

     

    Do you get the same erratic behaviour, if you start Aperture with the Shift-key held down, to defer the generation of previews?

  • 6. Re: Aperture crashes on rMBP, I need help
    saba01 Level 2 Level 2 (320 points)

    leonieDF, thanks for your time! I will try to answer your questions. Verify Disk brings nothing.

     

    Does Aperture actually crash with an error message and crash report, or is it just hanging?

     

    I can' t really tell  because when it happens, to whole computer freezes (At first I thought it would be hanging and waited 20 min) and has to hard restarted. I had the activity window open once but that freezes as well. In Console i only see the memory warnings. I don't think that the library contains bad files, I have by now worked on 4 different projects from 4 different years and it happens in all. The library was moved over by finder and repair permissions was run then; after the first incident Repair database was run.

     

    The strange thing is I can not reproduce it in a test set up, scowling through big projects back and forth works really well) But when I really sort out an Album it will happen (sooner or later)...

    I have tried to start with shift key, but had no "crash" but the memory count is off again after some time (around 9GB that it says I have..). I have to wait till I can sort out something (real work) before knowing for sure.

  • 7. Re: Aperture crashes on rMBP, I need help
    saba01 Level 2 Level 2 (320 points)

    Now it "crashed again!

    this is what Console captured just before hard restart:

     

    11/10/13 11:56:40.000 AM kernel[0]: memorystatus_thread: idle exiting pid 880 [com.apple.iCloud]

    11/10/13 11:56:40.212 AM com.apple.launchd[1]: (com.apple.iCloudHelper[880]) Exited: Killed: 9

    11/10/13 11:56:40.000 AM kernel[0]: memorystatus_thread: idle exiting pid 197 [xpcd]

    11/10/13 11:56:40.464 AM com.apple.launchd[1]: (com.apple.xpcd.F6010000-0000-0000-0000-000000000000[197]) Exited: Killed: 9

    11/10/13 11:56:40.000 AM kernel[0]: memorystatus_thread: idle exiting pid 879 [syncdefaultsd]

    11/10/13 11:56:40.720 AM com.apple.launchd.peruser.502[183]: (com.apple.syncdefaultsd[879]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.

    11/10/13 11:56:40.720 AM com.apple.launchd.peruser.502[183]: (com.apple.syncdefaultsd[879]) assertion failed: 13A3017: launchd + 39476 [73416961-6491-36E3-81D4-7636EA4B50E3]: 0x9

    11/10/13 11:56:40.000 AM kernel[0]: memorystatus_thread: idle exiting pid 878 [WiFiKeychainProx]

    11/10/13 11:56:40.962 AM com.apple.launchd.peruser.502[183]: (com.apple.wifi.WiFiKeychainProxy[878]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.

    11/10/13 11:56:40.962 AM com.apple.launchd.peruser.502[183]: (com.apple.wifi.WiFiKeychainProxy[878]) assertion failed: 13A3017: launchd + 39476 [73416961-6491-36E3-81D4-7636EA4B50E3]: 0x9

    11/10/13 11:56:41.193 AM WiFiKeychainProxy[884]: [NO client logger] <Sep 12 2013 14:48:11> WIFICLOUDSYNC WiFiCloudSyncEngineCreate: created...

    11/10/13 11:56:41.194 AM WiFiKeychainProxy[884]: [NO client logger] <Sep 12 2013 14:48:11> WIFICLOUDSYNC WiFiCloudSyncEngineRegisterCallbacks: WiFiCloudSyncEngineCallbacks version - 0, bundle id - com.apple.wifi.WiFiKeychainProxy

    11/10/13 11:56:41.000 AM kernel[0]: memorystatus_thread: idle exiting pid 373 [systemstatsd]

    11/10/13 11:56:41.212 AM com.apple.launchd[1]: (com.apple.systemstatsd[373]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.

    11/10/13 11:56:41.212 AM com.apple.launchd[1]: (com.apple.systemstatsd[373]) assertion failed: 13A3017: launchd + 39476 [73416961-6491-36E3-81D4-7636EA4B50E3]: 0x9

    11/10/13 11:56:41.454 AM xpcproxy[889]: assertion failed: 13A3017: xpcproxy + 3438 [3AB894B7-5C91-3252-A567-8EE4A311091E]: 0x2

    11/10/13 11:56:41.000 AM kernel[0]: memorystatus_thread: idle exiting pid 252 [com.apple.ShareK]

    11/10/13 11:56:41.467 AM com.apple.launchd[1]: (com.apple.ShareKitHelper[252]) Exited: Killed: 9

    11/10/13 11:56:41.567 AM syncdefaultsd[887]: *** -[IADomainCache init]: IA domains cache couldn't be read.

    11/10/13 11:56:41.567 AM syncdefaultsd[887]: -[IAPluginManager allAListPlugins] [546] -- *** warning: we're on the slow path.

    11/10/13 11:56:41.000 AM kernel[0]: memorystatus_thread: idle exiting pid 235 [AirPlayUIAgent]

    11/10/13 11:56:41.715 AM com.apple.launchd.peruser.502[183]: (com.apple.AirPlayUIAgent[235]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.

    11/10/13 11:56:41.715 AM com.apple.launchd.peruser.502[183]: (com.apple.AirPlayUIAgent[235]) assertion failed: 13A3017: launchd + 39476 [73416961-6491-36E3-81D4-7636EA4B50E3]: 0x9

    11/10/13 11:56:41.000 AM kernel[0]: memorystatus_thread: idle exiting pid 214 [com.apple.intern]

    11/10/13 11:56:41.975 AM com.apple.launchd[1]: (com.apple.internetaccounts[214]) Exited: Killed: 9

    11/10/13 11:56:42.000 AM kernel[0]: memorystatus_thread: idle exiting pid 24 [cfprefsd]

    11/10/13 11:56:42.220 AM com.apple.launchd[1]: (com.apple.cfprefsd.xpc.daemon[24]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.

    11/10/13 11:56:42.220 AM com.apple.launchd[1]: (com.apple.cfprefsd.xpc.daemon[24]) assertion failed: 13A3017: launchd + 39476 [73416961-6491-36E3-81D4-7636EA4B50E3]: 0x9

    11/10/13 11:56:42.000 AM kernel[0]: memorystatus_thread: idle exiting pid 194 [cfprefsd]

    11/10/13 11:56:42.471 AM com.apple.launchd.peruser.502[183]: (com.apple.cfprefsd.xpc.agent[194]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.

    11/10/13 11:56:42.471 AM com.apple.launchd.peruser.502[183]: (com.apple.cfprefsd.xpc.agent[194]) assertion failed: 13A3017: launchd + 39476 [73416961-6491-36E3-81D4-7636EA4B50E3]: 0x9

    11/10/13 11:56:42.574 AM com.apple.iCloudHelper[889]: AOSKit ERROR: Setup request failed, appleID=57570090, url=https://setup.icloud.com/setup/get_account_settings, requestHeaders=

    {

        "Accept-Language" = "en-us";

        Authorization = "Basic ...";

        "X-APNS-Token" = fd4eb04141c6d84db201ab03ec61118430cea0fa2862feaa1801485954727a84;

        "X-Aos-Accept-Tos" = false;

        "X-Mme-Client-Info" = "<MacBookPro11,3> <Mac OS X;10.9;13A3017> <com.apple.AOSKit/176>";

        "X-Mme-Country" = US;

        "X-Mme-Timezone" = EST;

    },

    error=Error Domain=AOSErrorDomain Code=5003 "The operation couldn’t be completed. (AOSErrorDomain error 5003.)" UserInfo=0x7ff02c832270 {HttpStatusCode=409, DialogInfo={

        AlternateButtonLabel = "";

        AlternateButtonLink = "";

        Body = "MOBILEME_TERMS_OF_SERVICE_UPDATE";

        DefaultButtonLabel = "mme.setupservice.SetupServiceJS.OK";

        DefaultButtonLink = "";

        DialogType = TOSDialog;

        ErrorID = "MOBILEME_TERMS_OF_SERVICE_UPDATE";

        Header = "";

        HelpLink = "";

        description = "This account needs to accept the ToS";

        localizedError = "MOBILEME_TERMS_OF_SERVICE_UPDATE";

        protocolVersion = 2;

    }}, httpStatusCode=409, responseHeaders=

    {

        "Cache-Control" = "no-cache, no-store, private";

        "Content-Encoding" = gzip;

        "Content-Length" = 404;

        "Content-Type" = "application/xml; charset=UTF-8";

        Date = "Sun, 10 Nov 2013 16:56:42 GMT";

        "X-Apple-Request-UUID" = "82efcf39-7fb4-4ca3-a158-12842f737206";

        "X-Responding-Instance" = "setupservice:11900301:st13p19ic-setupsvc003:8001:1T53:110272";

    },

    responseBody=

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

    <plist version="1.0">

              <dict>

                        <key>protocolVersion</key>

                        <string>2</string>

     

                        <key>DefaultButtonLabel</key>

                        <string>mme.setupservice.SetupServiceJS.OK</string>

     

                        <key>Body</key>

                        <string>MOBILEME_TERMS_OF_SERVICE_UPDATE</string>

     

                        <key>ErrorID</key>

                        <string>MOBILEME_TERMS_OF_SERVICE_UPDATE</string>

     

                        <key>DialogType</key>

                        <string>CustomDialog</string>

     

                        <key>AlternateButtonLink</key>

                        <string></string>

     

                        <key>AlternateButtonLabel</key>

                        <string></string>

     

                        <key>localizedError</key>

                        <string>MOBILEME_TERMS_OF_SERVICE_UPDATE</string>

     

                        <key>DefaultButtonLink</key>

                        <string></string>

     

                        <key>Header</key>

                        <string></string>

     

                        <key>HelpLink</key>

                        <string></string>

     

                        <key>description</key>

                        <string>This account needs to accept the ToS</string>

     

              </dict>

    </plist>

    11/10/13 11:57:17.312 AM com.apple.geod[443]: tcp_connection_destination_prepare_complete 16 connectx to 23.79.70.52#443 failed: 64 - Host is down

    11/10/13 11:57:17.313 AM com.apple.geod[443]: tcp_connection_handle_destination_prepare_complete 16 failed to connect

    11/10/13 11:57:17.313 AM com.apple.geod[443]: /SourceCache/GeoServices/GeoServices-702.14.9/GEOResourceManifestServerLocalPro xy.m:1492 connection error: Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo=0x7fbc9bf02b90 {NSUnderlyingError=0x7fbc9d927cf0 "Could not connect to the server.", NSErrorFailingURLStringKey=https://gspa35-ssl.ls.apple.com/geo_manifest/dynamic/config?application=geod&app lication_version=1&country_code=US&hardware=MacBookPro11,3&os=osx&os_build=13A30 17&os_version=10.9, NSErrorFailingURLKey=https://gspa35-ssl.ls.apple.com/geo_manifest/dynamic/config?application=geod&app lication_version=1&country_code=US&hardware=MacBookPro11,3&os=osx&os_build=13A30 17&os_version=10.9, NSLocalizedDescription=Could not connect to the server.}

    11/10/13 11:57:17.314 AM com.apple.geod[443]: Will retry manifest update in 320.000000 seconds

    11/10/13 12:01:16.000 PM bootlog[0]: BOOT_TIME 1384102876 0

     

     

    I have no idea what that all means!

  • 8. Re: Aperture crashes on rMBP, I need help
    firstlaunch Level 3 Level 3 (610 points)

    The log doesn't point to Aperture. Looks like a system issue. Do you have another log that notes Aperture?

  • 9. Re: Aperture crashes on rMBP, I need help
    Kirby Krieger Level 6 Level 6 (11,945 points)

    You're in good hands with the others here.  I would look into Mobile Me, and make sure you have nothing in Aperture relating to Mobile Me (first place to look: the Web tab of Aperture Preferences).

     

    And you might try disabling your memory-reporting and any other non-Apple system-metrics software.

  • 10. Re: Aperture crashes on rMBP, I need help
    léonie Level 9 Level 9 (51,720 points)

    I get in the status bar the used and free memory displayed in real time always.

    Is that iStat menu? Then make sure, that it has been updated to the latest version. I have seen quite a few reports, that the older version has been causing problems with Mavericks.