Hey Adam: Thanks for your reply. I added [testing retain] after the declaration of the variable, and I no longer get the wheel of death and my app freezing up.
In response to your comment about why I am using NSFileHandle, it is because in the final version of this app I will need to scan several hundred plist files and I would like the app to stay responsive during this process. I am aware that I could just use threading for this, but this seemed a less hassle way to accomplish the same thing. On 4/28/09 8:03 PM, "Adam R. Maxwell" <amaxw...@mac.com> wrote: > > On Apr 28, 2009, at 7:50 PM, Pierce Freeman wrote: > >> Thanks for your help. I don't get those strange errors anymore, >> however no >> if I try to save the NSDIctionary to a file (NSDictionary's >> writeToFile), > > You're releasing a variable that you don't own (testing). See the > Cocoa memory ownership rules at > http://developer.apple.com/DOCUMENTATION/Cocoa/Conceptual/MemoryMgmt/MemoryMgm > t.html > . > > Why are you using NSFileHandle asynchronous reading for a plist file, > anyway? This is unusual, to say the least. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
