If we keep the application up for long duration of time, this issue is seen more frequently.
Here, do you mean you simply leave the application as the foreground app for that length of time and it just 'happens', or do you mean the app is left at the front and after a long time, when you suddenly move to another app and back to yours it goes wrong [more often]? (You originally said after 15 - 20 switches back and forth, but this comment implies something else.) I'm trying to establish whether it is exclusively due to moving to another app and back to yours or occurs in other situations.
Going back to your original post, you describe capturing and rendering a bitmap to a surface and then removing it on pause.
1. Could you show us how you perform these two tasks, your code? I'm wondering if maybe the way you are doing it is leaking memory and eventually failing, or otherwise not releasing / unlocking resources properly, eventually reaching the limit.
2. If you avoid using the bitmap at all (no rendering from / on it - don't even create it), does the problem go away?
3. When you say 'captured and rendered', what exactly does the 'captured' part mean? Captured from where?
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
