Re: [newbie] NSString code so it won't leak
Re: [newbie] NSString code so it won't leak
- Subject: Re: [newbie] NSString code so it won't leak
- From: James DiPalma <email@hidden>
- Date: Thu, 12 Sep 2002 01:29:19 -0400
Interesting! I'm going to have to download OmniObjectMeter (and hope it
works better than ObjectAlloc on my iBook with 128MB of memory).
Given this information from Shawn, you might be able to prove that an
NSAutoreleasePool is not getting released by doing a poseAs and simply
NSLogging when it gets init-ed and when it gets released. If this
technique shows that an NSAutoreleasePool is leaking, then you can break
on its init method and figure out where it is leaking.
I don't think it will help though. You can protect yourself best that
you can by wrapping calls to extractWithData: like Shawn did, but I
think it will be difficult for anyone outside of Apple to fix an
NSAutoreleasePool leak inside of NSURLHandler.
If it is something else, then it is something else, but at least you
know it isn't your string code and that releasing filedata and that
NSURLHandler instance passed as sender.
-jim
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.