LoadLayout - Memory Issue

Can you upload your layout file with the images?

Hi Erel,

it is a little complicate to extract and seperate all the files. I can upload our current project state and send you a link per pm. It is difficult because we generate some views etc.

I've mailed our current project, maybe you can have a look.

Hi,

I tried to write a code module which initializes all bitmaps that are in use in different activities, so they will be loaded only once in memory. In the activities the panels will bet set by setbackgroundimage(bitmap).

But then we noticed some (for us) strange behaviors.

InitializeSample:
If I try to initialize 30 big pictures (normaly 1920x1054) with InitializeSample, by parameters maxwidth 960 and maxheight 527. But there comes an oom message at picture 15. If I load a picture that is in size bigger then the max parameters, for example 1280x703 then there is no oom message and the code runs fine. It feals like there is no difference between InitializeSample and only Initialize. Maybe there is a problem in the framework?

Different ram usage on different devices by same code:
The same code running (15 initialized pictures) would allocate 25 Mb Ram at my Galaxy Tab 7.7, at my Galaxy Note round 50. Is there a realtion to the pixel density or why is this double sized?

Another question for my calculations?
Is each pixel in a bitmap object represented as 32 bit integer?

Because of the unreliability of the garbage collector I tried this way, because I've no idea how to free up memory in the activities.

My only thoughts at the moment are to reduce the full hd pictures to smaller ones, load this at main init. And stretch this by gravity in panel?

Thanks in advance.

InitializeSample loads a sample of the image. The loaded image size will be equal or larger than these value.

I did go over your project, however it is pretty complicated. If you like you can create a small project that only deals with the images. I will help you optimize it.

Hi Erel,

thanks for looking at my code. How I mentioned it is comlicate to devide functionality from layout in our current state but I will try. What do you would like to see, layout files with big images loading ?

First back to my open question:
If each layout has a reference to a large background image and keeps this for time, it's no wonder that I go oom eventually, i think. Most Layout will hold sind large picture reference in full hd. Is this right?

InitializeSample loads a sample of the image. The loaded image size will be equal or larger than these value.

Click to expand...

Equal or Larger? In which relation? I couldn't get why it should be larger, I noticed the note in the explanation shown, but I didn't got it yet sorry.

Can you explain the different ram usage on different devices?

Regards Silentsea

Image sampling works by converting x pixels to a single pixel. The value of x depends on the the bitmap size compared to the desired size. x is an integer. So the result is that the loaded image is equal or larger than the desired size.

I tried your second program and it does crash. Note that you should not load the layout in Activity_Resume as the layout will be loaded multiple times.

You are trying to load huge background images. You will need to resize the images.

Can you explain the different ram usage on different devices?

Click to expand...

I'm not sure. It may be related to the different densities.

Erel as I comment, I load these in resume to simulate the behaviour because I've some activities with large layouts. I will of course load the layouts in the activity create. Just a sample.

But then, how can I support full hd pictures? I near future the first full hd display launches, it is annouced for june (Acer Iconia 700A).

Regards Silentsea

You can probably use the recycle method to free the resources before loading the new image. However the end result will be smooth as these are heavy operations.