Here's what I think you should do: 1. Search your code to make sure there's no CFRetain of a SecKeychainRef anywhere. Make sure you're not using any 3rd party libraries that might do so too. You want to make absolutely sure that the only way it can get CFRetain'ed after creation is in the system frameworks.
2. Change your call to CFRelease to CFMakeAllocatable, and verify that it doesn't complain about using CFMakeAllocatable on a SecKeychainRef. 3. Submit a bug report with the crash log and backtrace, stating that you don't CFRetain the SecKeychainRef anywhere, so it's being collected while it still has a non-zero CFRetain count *or* it's been zombified with a CFRetain somewhere in the system frameworks during some object's finalize. Either way, that's a bug in frameworks. 4. See what kind of answer you get. :) _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
