Finding memory leaks and memory bugs (was Re: [OT] Re: Don't leak memory!!)
Finding memory leaks and memory bugs (was Re: [OT] Re: Don't leak memory!!)
- Subject: Finding memory leaks and memory bugs (was Re: [OT] Re: Don't leak memory!!)
- From: "M. Uli Kusterer" <email@hidden>
- Date: Fri, 21 Nov 2003 17:04:07 +0100
It really is important to keep memory leaks in your applications to
a minimum. Use "top" to find applications that are leaking memory.
Look at the rightmost column, if it is growing a lot over time it
could be a memory leak that should be reported to the developer of
that app. Check in the list archives for instructions on how to use
the "leaks" tool for finding memory leaks in your own applications.
Folks,
what techniques do the Cocoa pros know to find such bugs? I.e.
memory leaks, double releases etc.?
-> I heard of NSZombieEnabled, and tried to turn it on as suggested
(on one cocoadev.com Wiki page), but I still get weird crashes and no
messages in my memory-buggy app.
-> ObjactAlloc sounds interesting, but last I tried it I had no idea
how to use it.
-> OmniObjectMeter sounded interesting as well, but what I know from
OmniGroup stuff, it usually means installing a whole kaboodle of
supporting frameworks... is it worth the hassle? Any success stories?
Anybody know any good articles, links, tech notes etc. that describe
how to look for memory problems in Cocoa? And how do I find out what
type an object had before an autorelease tool tried to dispose of it
again?
Thanks in advance for any clues, Wiki pages I haven't seen etc.
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
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.