[Xcode] Interpreting Object Alloc
[Xcode] Interpreting Object Alloc
- Subject: [Xcode] Interpreting Object Alloc
- From: Alexander von Below <email@hidden>
- Date: Fri, 31 Jul 2009 15:13:46 +0200
Hello List,
while my example for my issue is for the iPhone, I believe this is a
"Tools" question.
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.
I will gladly provide traces or sample code to reproduce this issue.
iPhone with 3.0 firmware (notice: not "or newer") is required.
Thanks for pointers or insight you may want to share
Alex
_______________________________________________
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