When an orientation occurs, your activity is being destroyed, and a new instance is created. The problem is that some references are still kept in memory.
Some useful resources to read: "Avoiding memory leaks" (http://android- developers.blogspot.com/2009/01/avoiding-memory-leaks.html) and "Faster screen orientation change" (http://android- developers.blogspot.com/2009/02/faster-screen-orientation- change.html). I had similar issues when loading bitmaps, and screen orientation changes would through an out of memory error almost every time at some point. The above links helped in solving the issue. Mihai Fonoage On Nov 3, 4:45 pm, fadden <[email protected]> wrote: > On Oct 30, 12:23 pm, Sekar <[email protected]> wrote: > > > 10-30 14:59:50.841: INFO/dalvikvm-heap(23490): Forcing collection of > > SoftReferences for 134217760-byte allocation > > Curiously, 134217760 is 0x08000020. Something went wrong in here. > > The original poster's allocation was 0x0A000024, also suspiciously > round. > > Is this easily repeatable? If so, can you file a bug on b.android.com > and attach the APK to the bug report? -- 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
