On Monday, 28 May 2012 at 03:20, Charlie Dickman wrote: > My application is using (leaking) too much memory and eventually dies because > no more can be allocated. I have used Instruments to measure the usage and > leaks and have addressed those it told me about. > > Now, however, Instruments indicates that memory reaches a steady state (no > more increases) yet the app continues to die for lack of memory. > > Does anyone know of a "next step" I can take to help track down this problem?
One thing I always find helpful in situations like this is to use Instruments' "Allocations" template, then, ignoring the graph and byte counts, sort the "Statistics" view at the bottom by "# Living" and see if there's anything that seems to be allocated a surprising number of times. Often there are large numbers of small objects that are really just handles to other things - for example, objects holding on to memory-mapped files, or OpenGL textures. These objects don't contribute much to the "Allocations" count, because they themselves are very small. The things they're holding on to also don't contribute, because they're not 'allocated' in a way the instrument tracks, but they could be taking up a lot of your address space. Jamie. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
