Sure, i've just trimmed it down to a single activity and 1 image being loaded ( this time not directly from the file system, but rather specified in the XML ). It loads a bit better, but still crashes:
Here's the source: http://dgoemans.com/Storage/ImageCrash.zip 1. Run the app 2. Image shows, hit the back button on the phone 3. Repeat Eventually i see in the debug output on hitting back that crash. After a few tries of that my homescreen crashed. After the homescreen crashed ( had to hit home to get it to force loading ), the app wouldn't load the image anymore and the above mentioned crash occured everytime on launching my app. All launches were done with the debugger attached, and my hardware is a Nexus One ( the one received from Google - thanks!! - for the device seeding program last year ). In the more advanced case - my actual app. I'm launching an intent from the wallpaper settings dialog. This crashes immediately, i assume because the Surface memory taken by the wallpaper rendering in the background pushes everything over the limit? On a side note, my confirm function - sending a bitmap through a bundle - should work right? I understand if you choose not to respond to that :) Finally, Thanks for responding on a Sunday, another reason i have an insane amount of respect for the Android team!! David Goemans -- 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
