On Jul 27, 2008, at 7:11 PM, Perry The Cynic wrote:
Remove the file /var/db/CodeEquivalenceDatabase and reboot. That
file has gotten corrupted and runs securityd into an endless memory-
eating loop that (usually) ends up running your system out of memory
and into the ground.
Securityd uses the code equivalence database to keep track of
programs that the user said are "the same". Sadly, it uses dbm for
that database (that was before sqlite showed up :-), and dbm has
this "interesting" corruption behavior. Happily, the code
equivalence database is not used at all for signed programs, and so
we'll be phasing out the entire equivalence feature some time
(relatively) soon.
(Meanwhile, you *could* sign your program during development. It
would get rid of the keychain dialog, if nothing else. You still
want to ditch the corrupted file, though.)
Cheers
-- perry
Sir, I am sending you the warmest of thoughts via telepathy. :-p
Thanks a bunch, and thanks for the tip about code signing, that sounds
like a bright idea.
- Greg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Apple-cdsa mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/apple-cdsa/email@hidden
