Bitmaps are going to take as much memory as they need for the grid of
pixels they represent.  If you want to store a giant image into a
giant bitmap (or even if you just want to create a giant empty bitmap)
you will consume that memory.

Android doesn't do so well with giant bitmaps that come and go because
they don't get garbage collected in the way you'd expect, and you'll
often run into memory problems if you attempt this.  It's a really
hairy topic with a lot of prior conversation around it that you can
easily search and find.

Doug

On Dec 30 2010, 1:37 pm, "Anton S." <[email protected]> wrote:
> Hi,
> I have a single image that is slightly larger than the android screen
> which I load into a ScrollView.
>
> My question is the following:
>
> Does android load the entire image into memory even though parts of it
> are invisible(need to be scrolled to),
> or does it use some kind of external/internal cache to store parts of
> the image that are not
> currently visible? If not, do you think it would be possible to
> implement something like this.
>
> Thanks!!

-- 
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

Reply via email to