On Nov 4, 2008, at 10:47 AM, Adam Fedor wrote:
On Nov 4, 2008, at 10:05 AM, David Duncan wrote:
While I don't see a leak in here, it can never hurt to simplify
your code. Try this instead.
Thanks, that is simpler, but it doesn't solve the problem. I've
tried many things. The easiest way to solve the problem is to
comment out this line:
//[rootLayer setContents: (id)imageRef];
Unfortunately, the app is not too useful in that case.
As others have said, you should be certain that this really is a
memory leak. Just because memory usage increases does not indicate a
leak, and in fact many parts of the OS can cause memory usage to go up
without leaks as there are a number of in-memory caches that are
created in order to speed up certain operations. You are likely
hitting one of these caches.
--
David Duncan
Apple DTS Animation and Printing
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
