Releasing after -getBitmap -- memory not recovered?
site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hey Team. I'm running Motion v3.0.2. Thanks a lot. m _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... Two questions: 1. Is there a way to check that an Image Well has a bitmap/texture without calling -getBitmap or -getTexture? I only need to check if it's empty. 2. I'm tracking down a memory leak in some software and I've found that if I watch the before and after memory usage during a -getBitmap and -release <bitmap>, I don't seem to recover everything allocated by -getBitmap. If a call to [parmsApi getBitmap:myMap ...] increases memory usage by 5 Megs, should I expect my 5 Megs back if I immediately call [myMap release]? Has anyone else had memory issues with -getBitmap? I'm watching usage with Activity Monitor (probably not the best way to watch memory, but I do see my internal image memory being released back properly). I may be barking put the wrong tree, but I'm wondering if other developers have experience anything similar. This email sent to site_archiver@lists.apple.com
participants (1)
-
Matt Rhodes