Re: Memory not being released in a timely manner
Re: Memory not being released in a timely manner
- Subject: Re: Memory not being released in a timely manner
- From: Jens Alfke <email@hidden>
- Date: Fri, 07 Jun 2013 11:08:46 -0700
On Jun 7, 2013, at 9:44 AM, Jonathan Taylor <email@hidden> wrote:
> Your suggestion of the VM Tracker instrument (which I had not spotted before) did bring up some interesting results though. These autoreleased image buffers that were causing the problem are definitely NOT reported at all by Allocations ("live" bytes stays stable at 250MB), but they do show up under VM Tracker as "CG image" and "CG raster data" - although I don't think there's a way of getting any further details about the buffers they provide the backing for?
Those sorts of buffers are probably magical at the kernel level — one of the jobs of CG/Quartz is to shuffle pixmaps between CPU and GPU memory, and doing that efficiently is important to overall graphics performance. I wouldn’t be surprised if there were special types of memory pages that were optimized for this, that don’t live in normal address space.
I just took a look at the Quartz Debug app and didn’t find any window for viewing memory usage, but someone might know of other tools. Sounds like it would be a good idea to add that to the regular memory-tracking instruments.
—Jens
_______________________________________________
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