Re: Memory Leak
Re: Memory Leak
- Subject: Re: Memory Leak
- From: "Sean McBride" <email@hidden>
- Date: Mon, 26 May 2008 11:14:18 -0400
- Organization: Rogue Research
On 5/26/08 9:59 AM, Scott Ribe said:
>> ...but if execution reaches the end of main() and memory is
>> still hanging around, there is no doubt that it is a leak.
>
>Not necessarily, could be cached data that is deliberately not released. (A
>long time ago I had to deal with an app where deleting all allocated memory
>could take up to 10-15 seconds at app quit!)
Quite right. My choice of the phrase "no doubt" was too strong. But in
the vast majority of cases it's true. IAC, better to print leaks at
quit and have a few false positives (and a way to add them to an
'ignore' list) than to not print at all. (Of course, such a feature
should be optional. Duh. :))
>If Apple were to address this problem, I'd much rather see them go a step
>further an API with a couple of calls: StartTrackingLeaksNow and
>PrintLeaksNow, or some such.
That would be great. It would also be nice if their frameworks did not
leak so much. Just create a 'Cocoa Document-based Application' from
Xcode stationary and play with it (About box, print, open, save, etc.)
and it leaks all kinds.
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden