Skip navigation
This discussion is archived

Updating app's Keychain access causing 'securityd' hang?

11068 Views 8 Replies Latest reply: Jan 22, 2007 12:54 AM by Rosyna RSS
Merlin Mann3 Calculating status...
Currently Being Moderated
Sep 3, 2006 4:59 PM
Recently, when I update an app and get the "Confirm Application Change" dialog box (related to re-authorizing Keychain permissions), clicking "Change All" to allow the change makes some Bad Things happen.

* dialog box stays up
* beachball spins
* everything slows way way down (GUI is mostly unresponsive, apps won't launch, etc.)
* Activity Monitor shows `securityd` and `kernel-task` each rocketing up in CPU and RAM usage (each grabs over a gig of virtual RAM and double digits of processor)

Things stay this way until I Force-Quit the app trying to update. Even then it gets only a little better -- securityd and kernel_task just keep gobbling way.

Since securityd can only be launched during a reboot, this leaves my system practically useless until I restart. Sometimes the dialog box itself goes away if I wait long enough (3-5 minutes?), but the processes still tear things up until I reboot.

What I've tried so far ("+" == tried numerous times)

* Keychain repair
* Renaming Keychain
* Disk Utility "Repair Disk"
* Disk Utility "Repair Disk Permissions"
* single-user mode: `fsck -y`
* single-user mode: Applejack for disk repair, cache clearing, preference checking, etc.
* Onyx for, well, clearing practically everything
* Combo update / system update
* Archive & Install reinstallation (from Disk)

Any idea what could be causing this?

It happens constantly with my beloved Quicksilver as well as the latest update of NetNewsWire. I'm thinking that _some entry_ in `login.keychain` has gotten hopelessly corrupted and is spinning the system into a tizzy.

What are my options apart from starting my 1800-item Keychain completely from scratch? Is there something beyond Keychain First Aid for resuscitating these items?

MacBook Pro   Mac OS X (10.4.7)   2GB RAM
  • Roger Goesele Calculating status...
    I have the same problem.

    An updated program tries to acces the keychain and securityd hangs... using huge amount of ram and everything get's slow.

    I also tried the same stuff... even tried it with an empty keychain (even with an empty user!)... but after using a new version of a program... the problem is back!

    MacBook Pro   Mac OS X (10.4.7)  
  • Alexander Clauss Calculating status...
    I've the same problem on my iMac (Intel, MacOSX 10.4.8). This started a few weeks ago. The exact date is unknown, because the problem shows up only when an application is updated and this application tries to access the keychain.

    Is there any solution available now? I've tried almost everything that was mentioned here (keychain repair etc), but no luck.

    The only workaround at the time is to manually update the application list for all passwords in the keychain application whenever an application is updated.

    iMac 20" (Intel)   Mac OS X (10.4.8)  
  • Paul Kalas1 Calculating status...
    I had a similar problem that I traced to in Utilities. Basically, with Airport off, my memory was OK. But with Airport ON and restart, securityd would consume all available RAM. I deleted all keychain passwords (and tried Keychain first aid, Keychain reset, etc.) and when I next connected to my wireless network I did NOT check the "Add to Keychain" item. Yet I found that the wireless network password DID appear as a new keychain item, and the memory hog securityd persisted. The solution was to go to System Preferences and configure the Network settings for Airport so that the "Options" item "Automatically add new networks..." is UNCHECKED (the default is for it to be checked). The effect is that you can leave Airport on, but when you restart you have to select your network and type in your password. I now have other passwords in my keychain but they do not cause memory hogging. To summarize, when the Airport/WPA security password is in the Keychain, it creates a memory hog out of securityd. With my solution it takes a little longer for Airport to find networks, and you have to type in your password to your network. But, the benefits are that #1, the computer starts quickly (22 sec from power on to login, and 13 seconds from login password return key to a functioning finder window), and #2, everything will run faster because you have more free memory.

    PB Pro, 2.13 Mhz, 2 GB RAM   Mac OS X (10.4.8)   no 2006-007 security update



  • Rosyna Calculating status...
    I'm posting this here just so it is here.

    But the fix can be found at

    Basically, it's due to a corrupted file.

    PowerMac G5 Dual 2.0 Ghz   Mac OS 9.1.x  


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • 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.