Home/ Questions/Q 8748015
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T12:27:13+00:00

I’m working on a android game. Problem starts when I try to use 3

  • 0

I’m working on a android game. Problem starts when I try to use 3 images for background. Images are 1280x720px and 100kb large.
The images are really not that big, so I’m bit confused why they should cause memory problem.

Note: Screen resolution is 800×400 so I cant really resize image by factor 2 as it is suggested on android developer
Note: I’m using HTC desire phone (here crash comes), I’ve also tried it on Samsung Galaxy S1 and on Samsung it works OK.

I’ve analysed memory in DDMS and what is strange is I found that Heap is only 3.5mb large. If I check rt.MaxMemory() it says I have around 25mb of space per app.

What comes to my mind is that heap isn’t “updating” fast enough to accommodate for larger photos/apps, so it crashes before it can load images despite being so small. Is there any way to manualy set heap size, or at least tell it to enlarge?

Here is code where I load images:

        Bitmap floorFront = BitmapFactory.decodeResource(host.getResources(), R.drawable.floor1);
        floorFront = Bitmap.createScaledBitmap(floorFront,host.realWidth,host.realHeight, true);
        floorFront = Bitmap.createBitmap(floorFront, 0, host.realHeight/2, host.realWidth, host.realHeight/2);
        host.addInstance(new Background(0,host.realHeight/2,host,floorFront,1));

        Bitmap floorBack = BitmapFactory.decodeResource(host.getResources(), R.drawable.sand);
        floorBack = Bitmap.createScaledBitmap(floorBack,host.realWidth,host.realHeight, true);
        floorBack = Bitmap.createBitmap(floorBack, 0, host.realHeight/2, host.realWidth, host.realHeight/2);
        host.addInstance(new Background(0,host.realHeight/2,host,floorBack,4));

        Bitmap floorRock = BitmapFactory.decodeResource(host.getResources(), R.drawable.foreground);
        floorRock = Bitmap.createScaledBitmap(floorRock,host.realWidth,host.realHeight, true);
        floorRock = Bitmap.createBitmap(floorRock, 0, host.realHeight/2, host.realWidth, host.realHeight/2);
        host.addInstance(new Background(0,host.realHeight/2,host,floorRock,0));

Here is exact error from LogCat:

 maxMemory:25165824
 memoryClass:24
 6144000-byte external allocation too large for tgis process.
 Out of memory: Heap Size=4739KB, Allocated=2399KB, Bitmap Size=18668KB
 VM won't let use allocate 6144000bytes

EDIT:
Now that you said it makes sense that bitmaps use “raw” size of image and not compressed. And after some research it seems that on android 2.2 and 2.3 bitmaps are not stored in heap therefore heap doesn’t increase after image is loaded.

I have one more question. We use those 3 images for background. We will now resize them a bit in vertical direction, but in horizontal we still kind of need them as they are. So the image will still be around 100x720px. The problem why we need 3 images is, so we can draw them separately and get layers effect (we can draw something between 2 images). What would be the best way to implement this to get desirable effect with as little of memory to use as possible?

Background:
background
Middle:
middle
Foreground
foreground

Note: This are just static backgrounds, animation happens around and between them.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’m not sure where you get that a 1280 x 720 pixel bitmap is 100KB. It’s really several megabytes. In bytes it is 1280 * 720 * however many bytes per pixel, usually 4 for images with transparency, or 2 for images without. It’s a huge amount of data for a cell phone to load. Maybe you are quoting the size of a compressed image format version such as PNG.

    Some tips to deal with memory usage problems:

    Use Bitmap.Config.RGB_565 input format on your factory if you don’t have any transparency. This saves space versus ARGB_8888.

    Set largeHeap to true on the application element in your AndroidManifest.xml.

    Make sure your bitmaps are not being scaled automatically based on devices density class. Place them in drawable-nodpi, for example, or disable the automatic scaling programatically, or provide a different bitmap for each density class in multiple drawable folders. If your bitmap is only in the drawable folder, it is going to get scaled 2x on XHDPI devices.

    Recycle bitmaps you are not using, e.g.:

    Bitmap floorFront = BitmapFactory.decodeResource(host.getResources(), R.drawable.floor1);
Bitmap floorFrontScaled = Bitmap.createScaledBitmap(floorFront,host.realWidth,host.realHeight, true);
floorFront.recycle();
floorFront = null;

Bitmap floorFrontCropped = Bitmap.createBitmap(floorFrontScaled, 0, host.realHeight/2, host.realWidth, host.realHeight/2);
host.addInstance(new Background(0,host.realHeight/2,host,floorFrontCropped,1));

    You can also manually run System.gc() at times. The system is supposed to do that for you before returning an OutOfMemoryError, but it doesn’t with bitmaps in Android because they have memory allocated outside Java.

    Note that when you read in a Bitmap, you can actually check if the size you need it at is a whole number divisor less than its size, then specify the factory should skip over pixels when loading. This can help on smaller resolution devices, which have correspondingly smaller memory limits.

    If you are not moving these background images separately, then draw them all to a single bitmap and use that instead of three at once.

    • 0