Re: Strange Memory leak
Re: Strange Memory leak
- Subject: Re: Strange Memory leak
- From: j o a r <email@hidden>
- Date: Tue, 16 May 2006 23:13:33 +0200
On 16 maj 2006, at 22.38, Jerrod Fowkes wrote:
Well for the most part I have kept things tidy.
Tidy?
What throws a red flag in this case is that the result is about 1 -
2 meg.
Result?
The tools would be handy, however when it comes down to it, I have
an object with a retain count too high, and it must be released so
that I can get my 1-2 meg back.
Have you ever heard of autorelease pools? Think about how they affect
you when you try to debug a memory management problem by looking only
at object retain counts! Some additional reading:
<http://www.cocoabuilder.com/archive/message/cocoa/2003/1/24/85457>
Keep in mind that memory leaks in the system frameworks are extremely
rare!
Also in this case It's a good thing that I did come across it with
this particular API call. I doubt those tools would have been able
to tell me that. I could be wrong though.
What you see might not be a "true" memory leak - and in that case it
should not reported as such. ObjectAlloc would still help you find
[1] which type of object that is being "leaked", and [2] where it is
"leaked".
I can only point you to the tools, but I can't force you to use them.
I can see why you hesitate to learn a new set of tools - of course
it's a bit of a pain. If you're serious about developing for the Mac,
you would need to learn about them sooner or later however (or some
one on your team would have to). In the end I definitively think that
it's worth it.
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden