How to handle out of memory exceptions in android

Question

am getting out of memory exception while loading image

String filePath = Environment.getExternalStorageDirectory()
                .getAbsolutePath() + File.separator + "/Omoto Images/background image.jpg";
        Bitmap bmp = BitmapFactory.decodeFile(filePath);
        page4image.setImageBitmap(bmp);

above code is for loading image from internal storage

What is the size of the image? What is the exact memory error from the logcat? — Daniel, Jun 17 '16 at 13:17
Possible duplicate of [android how to handle out of memory exception](http://stackoverflow.com/questions/4544919/android-how-to-handle-out-of-memory-exception) — Harshad Pansuriya, Jun 17 '16 at 13:20
Better is use Bitmap.Options RGB565 format, because it reduces size of image in 2 times. More, if it's needed, use sampling in options. — Petrov Dmitrii, Jun 17 '16 at 13:32
[USE THIS](https://stackoverflow.com/a/45632208/7616371) for solve this type error in android — , Aug 11 '17 at 10:00

score 1 · Answer 1 · answered Jun 17 '16 at 13:34

You can increase the heap memory of the application by using the largeheap="true" in AndroidManifest.

<application
        android:allowBackup="true"
        android:icon="@mipmap/ic_launcher"
        android:label="@string/app_name"
        android:largeHeap="true">

  </application>

But, it is not good practice to use it unless it is needed.

Official doc states

Whether your application's processes should be created with a large Dalvik heap. This applies to all processes created for the application. It only applies to the first application loaded into a process; if you're using a shared user ID to allow multiple applications to use a process, they all must use this option consistently or they will have unpredictable results. Most apps should not need this and should instead focus on reducing their overall memory usage for improved performance. Enabling this also does not guarantee a fixed increase in available memory, because some devices are constrained by their total available memory.

score 0 · Answer 2 · edited May 23 '17 at 12:22

0

You shouldn't handle the OutOfMemory exception. The good explanation is described here: Catching java.lang.OutOfMemoryError?

edited May 23 '17 at 12:22

Community

1
1

answered Jun 17 '16 at 13:25

Alex

617
4
15

How to handle out of memory exceptions in android

2 Answers2

Linked