Re: Use of Instruments.app remedies Core Data memory issue (!?)
Re: Use of Instruments.app remedies Core Data memory issue (!?)
- Subject: Re: Use of Instruments.app remedies Core Data memory issue (!?)
- From: Fritz Anderson <email@hidden>
- Date: Mon, 15 Jul 2013 13:53:00 -0500
On 14 Jul 2013, at 5:45 AM, Peter <email@hidden> wrote:
> When executing the identical sequence of searches with Instruments not being involved, the memory consumption increases single-mindedly and (depending on the number of hits for the query) after a couple of searches reaches the 1 GB level, ever growing from there.
>
> On the other hand, Instruments.app's memory footprint increases steadily while running but not in the same degree as my app's. Don't know if this is normal. Should be.
...
> The bottom line is: My app seems to behave very nicely while under surveillance of Instruments.app, but not on its own. Memory seems to get released while under surveillance, but not when not.
I'm inferring this from your question, but I want to be sure: How are you determining that your app's memory footprint is increasing when Instruments isn't attached? From Activity Monitor? Don't do that.
Activity Monitor tells you how much virtual memory your app has touched at one point or another. It says nothing about whether all of that memory is taken up by live objects, nor whether the pages for the former objects' addresses are still in RAM. It also includes the size of shared memory assets, like system libraries, that are going to be in RAM (or paged out) anyway, for other processes to use.
"Real Private Memory" is the closest thing to what you want, but even that isn't what you mean. Trust Instruments.
— F
_______________________________________________
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