We found there are very nasty memory and resource leaks in activities
and views that we don't know how to handle. I have test app that
basically starts activity A, that immediately starts activity B and B
starts A and so forth in infinite loop. Each activity displays its own
bitmap in image view.
There must be something else going on in your app. All standard apps
rely on onDestroy() being called and certainly do not do all you
mentioned in your message.
Be very careful with what you do with the Context. An Activity is a
Context and you might be leaking it without knowing it. What you are
2 matches
Mail list logo