Re: [Xcode] Interpreting Object Alloc
Re: [Xcode] Interpreting Object Alloc
- Subject: Re: [Xcode] Interpreting Object Alloc
- From: Bill Bumgarner <email@hidden>
- Date: Fri, 31 Jul 2009 08:51:03 -0700
On Jul 31, 2009, at 6:13 AM, Alexander von Below wrote:
While running our app (iPhone, 3.0) through instruments with Leaks
and ObjectAlloc, we noted that moving a UISlider would make the
graph in ObjectAlloc rise (and the number in NetBytes increase)
steadily. We trimmed the issue down to NIB-Ware (i.e. no code, just
a NIB with a UISlider), and the issue persisted.
I suspected this means our app is eating memory somewhere, even
though there were no leaks. I filed this as a bug (ID# 7015176), but
the engineers relied to me that the memory usage in Activity Monitor
did not increase. Indeed, I added the Activity Monitor instrument to
my trace and could not see any suspicious activity either.
This leads me to my question: Does ObjectAlloc tell me the truth? Is
it possible for the graph in ObjectAlloc to rise without the app
actually consuming the memory?
Or, to phrase this differently: What is the right way to ensure that
my app (or certain repetitive operations therein), Mac or iPhone, is
not eating memory away? I was alway under the impression that
ObjectAlloc is the tool to do that.
Are you tracking live objects or all objects ever?
If the latter, then you will see a steady increase in the object
counts if the tracking loop for a slider allocates and releases (to
the point of deallocation) objects.
If you are only tracking live objects (there is a checkbox for that),
then you shouldn't see the number grow any significant amount.
b.bum
_______________________________________________
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