I have a temporary workaround, but I'd still like to get this issue solved. As for the workaround, it seems that if the SeekBar's image is loaded before the camera picture, the memory error doesn't occur. Right now I have a boolean flag so that the first time my derived ImageView's onDraw method gets called it sets the image, rather than setting it in the xml layout. After this it trips the flag and subsequent onDraw calls get passed to the super. It's not ideal, but it works
On May 27, 2:30 pm, Max Salley <[email protected]> wrote: > I have an app that displays a camera picture as part of it, but if the > picture is in memory I get an out of memory exception when an > allocation of any size happens no matter what. If the app uses a > seekbar in addition to my PictureView the ~900 bytes it allocates are > too much. I even tried to load a 16x16 monochrome image on top of the > camera pic, but the 256 bytes were too much. I find it extremely > unlikely that the object containing the image is precisely the size so > that using it alone never causes a crash, but allocating even 256 more > bytes exceeds the memory budget. Does anybody know what the problem > is? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
