On Nov 4, 2008, at 8:23 AM, Matt Neuburg wrote:
On Sun, 02 Nov 2008 22:08:04 -0700, Adam Fedor <[EMAIL PROTECTED]> said:
I have a simple program with a memory leak that is driving me crazy.
It's basically a slide show application (no I can't use IKSlideShow),
where I repeatedly set an image in a CALayer. When run, the app
increases in memory size by 10MB or so every time a new image is
displayed.
This is NOT evidence for a leak. Do not attempt to second-guess that
Mac OS
X virtual memory management system. In fact, do not guess. The only
way to
know whether you have a leak is to use the memory analysis tools
(MallocDebug, Shark, what have you). m.
I have used ObjectAlloc and MallocDebug. In ObjectAlloc you can see
the graph of memory usage go up like a stair-step ad infinitum. If I
leave the program running long enough it crashes after running out of
memory. Both programs show large memory usage from CGSImageDataLock-
>img_data_lock (deep within a CATransactionCommit inside the
runloop). That doesn't really help me though.
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
