profiling my AIR application, I noticed Other Bitmap Memory growing over and over.
More specifically, every time I open a popup (through PopupManager.createPopup) a 10MB step seems to be added and never released.
After some try, i reached 500MB of Other Bitmap Memory (745MB of Total Memory), but looking as Win Task manager I found my application was using only 270MB.
So, is Other Bitmap Memory actually released even if Scout doesn't see it?
(I'm trying to identify leeks in my application, but this seems a Scout problem)
It's certainly possible that the memory allocated by the PopupManager isn't being tracked correctly - we'd need to look into it to be able to say what's going on. If you can send me an example of your content, or a smaller example that reproduces the issue, I'll get someone to look into it (firstname.lastname@example.org).
can you just give me a short info if there is such a problem with incorrect tracking of 'Other Bitmap Memory'?
Looks like i am observing this also. Was there some cause for this problem identified?