Thank you so much! These needs to be added to Android's documentation somewhere because it took many hours to come to this realization myself! I thought I was being smart by preserving my RemoteView's instance, but in reality I was keeping hard-references to Bitmaps. As a text clock widget updated by the minute, soon enough memory becomes a problem that way.
Tom On Thursday, May 21, 2009 5:03:26 PM UTC-4, Michael Elsdörfer wrote: > > I'm writing a widget. Currently, I'm have a simple ImageView, and > calling RemoteViews.setImageViewBitmap(). I'm using a service to do > the updates. > > I thought it might be a good idea to reuse an existing RemoteViews > instance, so I'm only querying it the first time around, and > subsequently simply call setImageViewBitmap() with the new image. > > This works well initially, but after some time I first start getting > "!!! FAILED BINDER TRANSACTION !!!" errors, and later, an OutOfMemory > exception. > > Simply creating a new RemoveViews instance every time works flawlessy > on the other hand. I'm just curios why that would be, any ideas? -- -- 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
