31 responses

  1. Tigerblood
    July 17, 2011

    Excellent! I wondered if there was a solution beyond disabling entirely. This gives me a couple of ideas for more permanent solutions, I’ll let you know if what I cook up works!

    • Kris Morf
      July 22, 2011

      Set the folder permissions to ‘Read Only’

  2. masterof0
    July 17, 2011

    I have set up Hazel from Noodlesoft to monitor the folder and automatically delete the folders for apps that I do not want maintain saved states for.

  3. Nonyo Business
    July 17, 2011

    Ha… ha, I’m guessing safari and chrome are two applications people will use this a lot for.

  4. masterof0
    July 17, 2011

    Use Hazel from Noodlesoft to monitor the folder and remove unwanted apps from saving state

  5. Me
    July 17, 2011

    Maye try making a folder with the name an app you don’t want to save state to use, and change the permissions to not include access for the user the app would be running as. If the apps/framework handle this gracefully that would prevent state from ever being saved without having to watch the directory.

    • Lance
      July 17, 2011

      That is a good solution and should work, just chmod -x would be sufficient but may cause Resume trouble

  6. PaSav
    July 17, 2011

    Fast way to go to your ~/Library folder : Hold Alt -> Go -> Library will appear.

  7. Dan
    July 17, 2011

    I’m thinking that touching blank files inside the folder and then locking them would prevent new Resume states from being written. I’ll have to test once Lion’s released.

  8. alinaonme
    July 18, 2011

    a good solution for me

    sudo chmod -R u-w,go= ~/Library/Saved\ Application\ State

  9. albinoz
    July 18, 2011

    this remove state of resume, but not resume :/

  10. _udo_
    July 18, 2011

    If frequent removal of several saved application states is indicated then an Apple script should be the fastest solution–with the Scripts Folder on the menu bar.

    • Ex2bot
      July 19, 2011

      I was thinking of a quick Automator script.

      • Tim
        July 21, 2011

        I created an Automator script to move all the files to the trash. (I have no need or desire for any of the saved states.) My workflow is (1) Get Specified Finder Items – Saved Application State folder; (2) Get Folder Contents; (3) Move Finder Items to Trash. I saved this as an application and then coupled it with some restart and shutdown applescripts I had already created.

        Thanks, by the way, for this article! I was going nuts every time my computer restarted and all of those programs were relaunching.

  11. rezecib
    July 19, 2011

    My first thought on how to disable this for a given application is to delete the contents of the folder, then make it unwritable, either by changing the permissions or redirecting it to /dev/null. That’s my standard technique where a program keeps creating a file that I don’t want it to, and I think it should work in this case, assuming Apple programmed it well enough to be able to handle that folder being empty, which is extremely likely.

  12. John
    July 19, 2011

    Now why didn’t apple just ad an extra right click option on a dock icon or a click and hold to “jiggle” running apps so you can quit them completely like in iOS?

  13. Stuart Rowlands
    July 20, 2011

    I disable this behaviour on an app-by-app basis, I find it useful (for some apps at least!)

    Basically do:

    chown -w ~/Library/Saved Application State/app_folder_here

    I’ve written a quick guide here:

  14. Kris Morf
    July 22, 2011

    You can set permissions on the folder to “Read Only” to completely disable the feature.

  15. Robert
    July 22, 2011

    How do you delete a simple PDF file anymore without manually throwing in trash? I love the POTENTIAL and the BOOT sequence with a live terminal… be great to get a linux or some over OS for these future trying times as I have had — OS keeps freezing, locking up or crashing. Apple suggests repair permissions or restart or shut down – sure the solution, right… I’ve looked into the recovery EFI and poked around in terminal – wish these things came with more docs to tweak and repair / fix issues like this. This morning was the first time I actually recovered to any STATE at all, all the other times it froze or keyboard went dead, nothing… well it restored it to ALMOST the same state – the windows were correct, and open apps but the files on the desktop were all neatly in a pile – and OH yeah APPLE if you are listening – none of the crashes would allow me, even after clicking or using a command – to pull up FORCE Quit – That’s a usually easy fix for many ISSUES without taking down the whole platform, not in LION YET… and the few times I got it to open, sometimes it would actually force an app to quit and sometimes it refused… and YES I have what’s suppose to be a compatible make model and oil change, I’ve had over 40 Macs and this system has STUD potential but is a 1 second let down.

  16. Elizabeth
    July 29, 2011

    I have followed the instructions for disabling the application saved status for Pages, as I usually have a million different documents open and I liked restarting my computer with a blank slate. Deleting the saved application status folder and disabling the resume function seemed to have helped, except in the instance when I have opened a .doc file and I quit Pages. Normally I would be prompted to save it as a .pages file, but now it just quits, then has the (unsaved) .doc file open again when I restart Pages. This is bloody annoying. If anyone has any tips I would greatly appreciate it.
    PS. I’m sure this function (and many more new Lion tools) would work as it’s meant to on a newer machine than mine, but I’m not sure my poor old ’08 MacBook can handle it. I’m getting a lot of spinning wheel of death. Any other recommendations to make the system a little less sluggish?

  17. Bob
    August 16, 2011

    Nothing above works for me.

  18. Michael Johnston
    March 9, 2012

    The problem is that with many apps, Lion does not observe when windows are closed. So once you’ve ever opened a window, it will always open every time you start that app, no matter how many times you close it again.

    This is incredibly annoying.

  19. Jawed
    April 10, 2012

    best solution for application that is not responding in Mac OS X is “Force Quite”:


    it worked for me!

  20. Rob
    April 15, 2012

    This is the kind of that drives me nuts about apple sometimes. I have a 2g macbook. Often I have to quit apps to save memory and OSX opens the all up again after restart. JUST GIVE US CONTROL! not workarounds for geeks!

  21. Prasad
    November 30, 2012

    Great tutorial. Thanks.

  22. Callum
    March 29, 2013

    can i do this on other versions of the mac ?

    • Paul
      March 29, 2013

      Yes it works in OS X Mountain Lion as well.

  23. James
    December 6, 2013

    Brilliant you just saved me the most frustrating time and got files working you’re stars!!

Leave a Reply




Back to top
mobile desktop