Best way to find memory leaks
Best way to find memory leaks
- Subject: Best way to find memory leaks
- From: Ken Tozier <email@hidden>
- Date: Fri, 25 Jun 2004 10:02:29 -0400
I ran the object alloc utility on my app and it turns out I have some
serious memory leaks, many (but not all) of which seem to be what I
thought were temporary strings allocated with the + (id) class methods
inside loops.
For simplicity's sake, all my allocation uses the various + (id) xxx
class methods but it seems that an awful lot of stuff isn't getting
released. On a machine with 1 GB of ram, the program runs for about 10
minutes and then just stops. No "out of memory errors" but looking at
the bar charts in Object Alloc shows a few bars that are off the charts
for memory usage. Problem is Obj Alloc is useless for tracking down the
problem as the culprit usually has a cryptic name like "libxxx 23".
How do others find their leaks?
Ken
_______________________________________________
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.