Skip navigation

aperture locked up and can't quit

1148 Views 14 Replies Latest reply: Mar 3, 2012 10:31 AM by hotwheels 22 RSS
hotwheels 22 Level 1 Level 1 (0 points)
Currently Being Moderated
Mar 1, 2012 3:23 PM

my machine appears to have ground to a near total halt and i can hear the macpro churning. i am trying to close out of aperture by clicking CLOSE from the Dock Icon or QUIT from the pulldown to no avail.

 

given that I am also closing out other software in an attempt to shut down and restart is there a correct way to shut down aperture and/or things to watch out for in order to protect my database integrity/

 

TIA

  • Kirby Krieger Level 6 Level 6 (11,550 points)
    Currently Being Moderated
    Mar 1, 2012 3:33 PM (in response to hotwheels 22)

    There is no good alternative.

     

    IME, the choice is:

    - let it run (perhaps for a couple of hours) and see if it finishes processing and either closes or can be closed

    - Force Quit.

     

    Force Quitting is always a bad idea, especially for databases.  You should run "Repair Library" after any Force-Quit.

     

    At the least, if you can, give it twenty minutes to think about things.

  • Kirby Krieger Level 6 Level 6 (11,550 points)
    Currently Being Moderated
    Mar 1, 2012 7:57 PM (in response to hotwheels 22)

    "→Shut Down" is always preferred over Force Quit.  If Aperture is hung, you won't be able to shut down the computer via "→Shut Down", in which case the only way to shut down is to Force Quit and then "→Shut Down"

     

    There is no size limit in terms of number of Images or file size of the Aperture package that should cause any concern.  (I have run 500 GB Libraries with nearly half a million Images on Mac laptops with 4 GB of RAM.)  The application is (very) hardware intensive, but it doesn't seem to get noticeably worse as one's Library grows, as long as one takes the usual precautions for running Aperture well.  Don't over-stuff your drives.  Imho, performance is not a good reason to divide a Library.  If you need more drive space, buy it.  If you need better performance, splitting a Library is not likely to make any difference.

  • 1 Open Loop Calculating status...
    Currently Being Moderated
    Mar 3, 2012 5:58 AM (in response to Kirby Krieger)

    Why is shut down better than force quit? Assuming you can shut down.

  • léonie Level 8 Level 8 (46,355 points)
    Currently Being Moderated
    Mar 3, 2012 6:49 AM (in response to 1 Open Loop)

    When you Force Quit, this will send the signals SIGKILL and SIGSTOP to all processes. These signals cannot be caught, blocked, or ignored - it is like pulling the plug. The processes will exit immediately, without an opportunity of closing any files properly and without finishing database transactions. Your Aperture library may be left in an inconsistent state and need repairing.

     

    Shutdown will send SIGTERM (if I remember correctly)- this signal can be caught and ignored by the processes, so they can finish essential transactions and can close open files before they exit. No need for database repair, if you exit this way.

  • 1 Open Loop Level 2 Level 2 (350 points)
    Currently Being Moderated
    Mar 3, 2012 7:47 AM (in response to léonie)

    I never knew that.

     

    Thanks. I will Shutdown from now on.

     

    Does Reboot send the same SIGTERM commands?

  • léonie Level 8 Level 8 (46,355 points)
    Currently Being Moderated
    Mar 3, 2012 8:38 AM (in response to 1 Open Loop)

    Does Reboot send the same SIGTERM commands?

    I can only guess (I am travelling right now and away from my manuals) - but since Reboot is a "Shutdown" followed by "Restart" it should  do the same.

     

    The SIGTerm is the signal that is usually sent by "Quit" - and to shutdown is a way to send the same signals as the  "Quit" button, if the user interface is unresponsive. This may happen, if you run into a deadlock or a program performs a task that takes forever right in the thread that should respond to user interactions.

  • 1 Open Loop Level 2 Level 2 (350 points)
    Currently Being Moderated
    Mar 3, 2012 8:42 AM (in response to léonie)

    leonieDF wrote:

    (I am travelling right now and away from my manuals)

     

    Well, close your laptop, put it away and keep your eyes on the road. (I hope your not using a Mac Pro)

     

    But, thanks.

  • léonie Level 8 Level 8 (46,355 points)
    Currently Being Moderated
    Mar 3, 2012 8:49 AM (in response to hotwheels 22)

    See my answer above:

     

    If the quit button is unresponsive, a shutdown will send the same signal as the "Quit" button would. So you can get the message trough, even thru a blocked GUI.

     

    But the "SIGTERM" can be caught by the  program - if a program is not willing to quit, you may have to force quit in the end.

     

    You could do the same from the Terminal, if you know how to find out the process id of the parent process of an application.

  • léonie Level 8 Level 8 (46,355 points)
    Currently Being Moderated
    Mar 3, 2012 8:54 AM (in response to 1 Open Loop)

    Well, close your laptop, put it away and keep your eyes on the road.

    Thanks for your concern for my safety, Kevin,  I am not the one sitting behind the wheel ...

  • léonie Level 8 Level 8 (46,355 points)
    Currently Being Moderated
    Mar 3, 2012 9:17 AM (in response to hotwheels 22)

    Sorry, Jon, I got interrupted by Apple maintainance again, before I could answer the second part of your question:

     

    If correct (or close) is this for programs on the Mac that contain databases or for all Mac Software...?

    You should avoid to force quit any program that keeps persistent data or modifies data of other programs: databases, programs that write documents or other files, programs that keeps preference lists, it applies to nearly all programs.

     

    Regards

    Léonie

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.