java.lang.OutOfMemoryError Even in a try-catch block?

Question

My application crashes, showing this in logcat:

java.lang.OutOfMemoryError: (Heap Size=39047KB, Allocated=19932KB) at android.graphics.BitmapFactory.nativeDecodeFile(Native Method) at android.graphics.BitmapFactory.decodeFile(BitmapFactory.java:373) at android.graphics.BitmapFactory.decodeFile(BitmapFactory.java:443) at com.mApp.mobileapp.mActivity.onActivityResult(mActivity.java:196) at android.support.v4.app.FragmentActivity.onActivityResult(FragmentActivity.java:153) at android.app.Activity.dispatchActivityResult(Activity.java:4752) at android.app.ActivityThread.deliverResults(ActivityThread.java:3449) at android.app.ActivityThread.handleSendResult(ActivityThread.java:3503) at android.app.ActivityThread.access$1100(ActivityThread.java:144) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1320) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:156) at android.app.ActivityThread.main(ActivityThread.java:5109) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:511) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:991) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:758) at dalvik.system.NativeStart.main(Native Method)

While running this code:

String selectedImagePath = data.getStringExtra("imageByteCode"); try { File imageFile = new File(selectedImagePath); Bitmap bitmap = BitmapFactory.decodeFile(imageFile .getAbsolutePath());//line 196 ByteArrayOutputStream baos = new ByteArrayOutputStream(); bitmap.compress(Bitmap.CompressFormat.JPEG, 100, baos); base64code = selectedImagePath; mImage.setImageBitmap(bitmap); } catch (Exception e) { }

Since i was catching it, i never expected it to crash the app. selectedImagePath is the path of the selected image on the SD card, which never exceeds 3m.b but Heap Size=39047KB, Allocated=19932KB ??

Thank You

Henry · Accepted Answer · 2013-02-11 13:08:11Z

11

You did not catch it. OutOfMemoryError is derived from Error, not from Exception. It is an Error because normally an application is not supposed to catch it, there is close to nothing your application can do to recover.

answered Feb 11, 2013 at 13:08

Henry

43.9k7 gold badges75 silver badges89 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Archie.bpgc Over a year ago

great. But none of the images are more than 3mb in size so, i might not be handling bitmap memory allocation the right way?

Henry Over a year ago

For loading large images this may help: stackoverflow.com/questions/2798756/…

Naskov · Accepted Answer · 2016-07-19 10:46:26Z

Place android:largeHeap="true" in your Manifest file under the application tag.

The largeHeap tells the VM to give you more RAM so you can manage big bitmaps and Strings. LargeHeap works in api 12+.

And if you want to catch the error with try/catch block you need to use

try { }catch (OutOfMemoryError e) { // TODO: handle exception }

If you are experiencing this while building the project in Android Studio

Error:Uncaught translation error: java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: GC overhead limit exceeded

add in your build.gradle file

dexOptions { javaMaxHeapSize "4g" }

Epic Answer. A lot of information in as few words as possible. +1 largeheap. +1 OutOfMemoryError can be recovered from (sometimes) and this is the code to do it. In this situation the asker was trying to open an image. Using try catch(OutOfMemoryError) this won't crash the app and an error message can be displayed to the user.
I still need to use a better image caching library, but this gives me some leeway! thanks (going from loopj to Universal Image Loader)
android:largeHeap="true" is usually a bad idea, see here : stackoverflow.com/a/30930239/11278124

Collectives™ on Stack Overflow

java.lang.OutOfMemoryError Even in a try-catch block?

2 Answers 2

2 Comments

4 Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

4 Comments

Linked

Related