ansaurus

Question

Answer 1

A:

I did the following to take the image and resize it on the fly. Hope this helps

 Bitmap bm;
 bm = Bitmap.createScaledBitmap(BitmapFactory.decodeFile(filepath),100, 100, true);
 mPicture = new ImageView(context);
 mPicture.setImageBitmap(bm);

Chrispix 2009-02-16 06:23:31

This approach scales the bitmap. But it doesn't solve the OutOfMemory issue because the full bitmap is being decoded anyway.

Fedor 2010-01-05 06:51:34

I will see if I can look at my old code, but I think it did solve my out of memory issues. Will double check my old code.

Chrispix 2010-09-22 17:19:38

Answer 2

+36 A:

To fix OutOfMemory you should do something like that:

BitmapFactory.Options options=new BitmapFactory.Options();
options.inSampleSize = 8;
Bitmap preview_bitmap=BitmapFactory.decodeStream(is,null,options);

This inSampleSize option reduces memory consumption.

Here's a complete method. First it reads image size without decoding the content itself. Then it finds the best inSampleSize value, it should be a power of 2. And finally the image is decoded.

//decodes image and scales it to reduce memory consumption
private Bitmap decodeFile(File f){
    try {
        //Decode image size
        BitmapFactory.Options o = new BitmapFactory.Options();
        o.inJustDecodeBounds = true;
        BitmapFactory.decodeStream(new FileInputStream(f),null,o);

        //The new size we want to scale to
        final int REQUIRED_SIZE=70;

        //Find the correct scale value. It should be the power of 2.
        int width_tmp=o.outWidth, height_tmp=o.outHeight;
        int scale=1;
        while(true){
            if(width_tmp/2<REQUIRED_SIZE || height_tmp/2<REQUIRED_SIZE)
                break;
            width_tmp/=2;
            height_tmp/=2;
            scale++;
        }

        //Decode with inSampleSize
        BitmapFactory.Options o2 = new BitmapFactory.Options();
        o2.inSampleSize=scale;
        return BitmapFactory.decodeStream(new FileInputStream(f), null, o2);
    } catch (FileNotFoundException e) {}
    return null;
}

Fedor 2009-05-05 09:00:14

Note that 10 may not be the best value for inSampleSize though, the documentation suggests using powers of 2.

Mirko Nasato 2010-05-28 11:59:26

Right. I've edited the answer.

Fedor 2010-05-28 12:23:13

I love you, Fedor!!!

Cristian 2010-05-30 22:33:12

I'm facing the same problem as Chrispix, but I don't think the solution here really solves the problem, but rather sidesteps it. Changing the sample size reduces the amount of memory used (at the cost of image quality, which is probably okay for an image preview), but it will not prevent the exception if a large enough image stream is decoded, of if multiple image streams are decoded.If I find a better solution (and there may not be one) I'll post an answer here.

Flynn81 2010-07-08 15:19:17

You only need an appropriate size to match the screen in pixel density, for zooming in and such you can take a sample of the image at a higher density.

stealthcopter 2010-08-08 22:43:15

Answer 3

A:

I had the same problem and Fedor's solution is effective.

Jay Pogi 2010-03-17 15:14:02

Answer 4

A:

u should first clear all the view... than u can try... means bcz of mobile memory is limited... bitmap object consumes more memory compare to other. i had getting the same problem but after removing all previously created view it worked correctly ... Enjoy....

Ashish Mishra 2010-04-14 09:39:12

Answer 5

A:

hello, as I'm beginner in Android I have problem with memory - after only 2-3 minutes I get Force Close and outOfMemory Error.

I have only onCreate (I know, stupid, but I didn't knew for anything else as I started only few weeks ago) and inside I have...

@Override
 public void onCreate(Bundle savedInstanceState) {
  super.onCreate(savedInstanceState);
  setContentView(R.layout.main);

  many lines of code...manipulating with SQLite databases...

}

inside main XML layout I have many images, small, big (background) and so on...How can I on every onCreate "delete" all content from memory that was before in it - so when I open activity again, it deletes all images and everything out and insert the new (old) one inside. "Little" awkward but that's only thing I have on mind.

Also, inside "many lines of code" I don't declare any images!

Or simply, how can I "bypass" outOfMemoryError? Do I have to do something like this?

 @Override
     public void onCreate(Bundle savedInstanceState) {
      super.onCreate(savedInstanceState);

        BitmapFactory.Options options=new BitmapFactory.Options();
        options.inSampleSize = 8;
        Bitmap buildingBitmap = BitmapFactory.decodeResource(null,R.drawable.background,options);

if (buildingBitmap != null)
        {
        buildingBitmap.recycle();
        System.gc();
        buildingBitmap = null;
        }

      setContentView(R.layout.main);

      many lines of code...manipulating with SQLite databases...

    }

or...? Also on other activity is everything "the same" except I have multiple overlays, how can I "erase" (recycle) them also? Thank you for any help.

*currently, I'm not searching for fastest, most "correct" or better solution, I just want something that it's not crashing all the time

svebee 2010-06-10 14:21:55

this should be a separate question... not an answer to a related question

gary comtois 2010-09-04 18:24:43

Answer 6

A:

Hello Fedor, I was having the same issue and your proposed solution worked for me but now image's quality is very poor. How to deal with it?

Sam 2010-06-29 14:18:00

Answer 7

+2 A:

May be the answer mentioned on this site might solve the issue...

BitmapFactory.Options options = new BitmapFactory.Options();
options.inTempStorage = new byte[16*1024];

bitmapImage = BitmapFactory.decodeFile(path,opt);

Sash 2010-07-19 10:20:24

Tried this solution. Unfortunately no effect. Still OutOfMemory for large photos.

Fedor 2010-07-27 00:39:55

I also tried this and still get an OutOfMemory exception too.

stealthcopter 2010-09-04 22:36:49

I don't think this helps, and the reason I don't is because I read the source code for decodeFile and the source code does this itself if you don't.

Max Howell 2010-09-08 13:34:13

Answer 8

A:

Fedor.... Thnaks a lot.... Excellent solution.

Bilal 2010-08-05 10:06:40

Answer 9

+1 A:

You are most likely suffering from this Android bug:

http://code.google.com/p/android/issues/detail?id=8488

The bug report contains a testcase.

Andreas Schildbach 2010-08-08 18:13:41

Answer 10

+4 A:

I've made a small improvement to Fedor's code. It basically does the same, but without the (in my opinion) ugly while loop and it always results in a power of two. Kudos to Fedor for making the original solution, I was stuck until I found his, and then I was able to make this one :)

private Bitmap decodeFile(File f){
    Bitmap b = null;
    try {
        //Decode image size
        BitmapFactory.Options o = new BitmapFactory.Options();
        o.inJustDecodeBounds = true;
        BitmapFactory.decodeStream(new FileInputStream(f), null, o);
        int scale = 1;
        if (o.outHeight > IMAGE_MAX_SIZE || o.outWidth > IMAGE_MAX_SIZE) {
            scale = Math.pow(2, (int) Math.round(Math.log(IMAGE_MAX_SIZE / (double) Math.max(o.outHeight, o.outWidth)) / Math.log(0.5)));
        }

        //Decode with inSampleSize
        BitmapFactory.Options o2 = new BitmapFactory.Options();
        o2.inSampleSize = scale;
        b = BitmapFactory.decodeStream(new FileInputStream(f), null, o2);
    } catch (FileNotFoundException e) {
    }
    return b;
}

Thomas Vervest 2010-08-23 15:25:32

Yes you're right while is not so beautiful. I just tried to make it clear to everyone. Thanks for your code.

Fedor 2010-08-24 01:32:46

This (and Fedor's code) helped point me in the right direction. Thanks!

Jake Basile 2010-09-23 13:38:33

@Thomas Vervest - There's a big problem with that code. ^ doesn't raise 2 to a power, it xors 2 with the result. You want Math.pow(2.0, ...). Otherwise, this looks good.

DougW 2010-10-13 07:42:56

Ooh, that's a very good one! My bad, I'll correct it immediately, thanks for the reply!

Thomas Vervest 2010-10-26 09:20:51

Answer 11

A:

Hey Sam, Your problem is probably because of the scale value. It should always be a power of two, if you use my code it should solve your problem :)

Thomas Vervest 2010-08-23 15:29:06

Answer 12

A:

Can anybody help with another problem - it seemes that some memory(especially using list adapters with bitmaps) doesn't release even when you "null'ing" adapters and recycling bitmaps. Is there any strategy for an absolute memory cleaning? Resizing is not an option because bitmaps already have small size... anyway thnx for the help.

Alexander 2010-09-06 17:18:39

ansaurus

tags:

views:

answers:

Android: Strange out of memory issue

related questions