Re: Checking for memory leaks with Instruments
Re: Checking for memory leaks with Instruments
- Subject: Re: Checking for memory leaks with Instruments
- From: "I. Savant" <email@hidden>
- Date: Fri, 29 Aug 2008 14:08:03 -0400
On Fri, Aug 29, 2008 at 1:49 PM, Christian Giordano
<email@hidden> wrote:
> On th e Leaks Instrument though,
> no leak is shown. I can't really find why the ram continues to
> increase, and my app is really simple. I tested then a sample app from
> apple and this a part having an increase memory usage, like mine, also
> shown some memory leaks in the related instrument. What am I missing?
> I followed this tutorial as well but no leak was found on my app.
Maybe because there ARE no leaks. :-) Have you considered that you
might have some container sitting around somewhere (an array or a set)
that keeps collecting stuff and not letting go? A 'leak' is (in
general) an object with no reference with a retain count >0 ... it
will never be released and this is a memory management error. Runaway
memory usage is not necessarily a leak, however.
Without more (a LOT more) information about your application, it's
hard (if not impossible) to tell you where your problem is.
--
I.S.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden