Releasing after -getBitmap -- memory not recovered?
Releasing after -getBitmap -- memory not recovered?
- Subject: Releasing after -getBitmap -- memory not recovered?
- From: Matt Rhodes <email@hidden>
- Date: Thu, 16 Oct 2008 17:27:18 -0700
Hey Team.
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 running Motion v3.0.2.
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.
Thanks a lot.
m
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden