Google Play Console crash reporting java.lang.OutOfMemoryError

Question

I get a crash report on the Google Play Console on this device: Samsung Galaxy A5(2016) (a5xelte),

java.lang.OutOfMemoryError: 

  at dalvik.system.VMRuntime.newNonMovableArray (Native Method)

  at android.graphics.BitmapFactory.nativeDecodeAsset (Native Method)

  at android.graphics.BitmapFactory.decodeStream (BitmapFactory.java:700)

  at android.graphics.BitmapFactory.decodeResourceStream (BitmapFactory.java:535)

  at android.graphics.drawable.Drawable.createFromResourceStream (Drawable.java:1179)

  at android.content.res.ResourcesImpl.loadDrawableForCookie (ResourcesImpl.java:770)

  at android.content.res.ResourcesImpl.loadDrawable (ResourcesImpl.java:621)

  at android.content.res.Resources.loadDrawable (Resources.java:1729)

  at android.content.res.TypedArray.getDrawable (TypedArray.java:945)

  at android.widget.ImageView.<init> (ImageView.java:157)

  at android.widget.ImageView.<init> (ImageView.java:145)

  at android.support.v7.widget.AppCompatImageView.<init> (AppCompatImageView.java:60)

  at android.support.v7.widget.AppCompatImageView.<init> (AppCompatImageView.java:56)

  at android.support.v7.internal.app.AppCompatViewInflater.createView (AppCompatViewInflater.java:98)

  at android.support.v7.app.AppCompatDelegateImplV7.createView (AppCompatDelegateImplV7.java:926)

  at android.support.v7.app.AppCompatDelegateImplV7.onCreateView (AppCompatDelegateImplV7.java:980)

  at android.support.v4.view.LayoutInflaterCompatHC$FactoryWrapperHC.onCreateView (LayoutInflaterCompatHC.java:44)

  at android.view.LayoutInflater$FactoryMerger.onCreateView (LayoutInflater.java:193)

  at android.view.LayoutInflater.createViewFromTag (LayoutInflater.java:776)

  at android.view.LayoutInflater.createViewFromTag (LayoutInflater.java:734)

  at android.view.LayoutInflater.rInflate (LayoutInflater.java:865)

  at android.view.LayoutInflater.rInflateChildren (LayoutInflater.java:828)

  at android.view.LayoutInflater.rInflate (LayoutInflater.java:873)

  at android.view.LayoutInflater.rInflateChildren (LayoutInflater.java:828)

  at android.view.LayoutInflater.rInflate (LayoutInflater.java:873)

  at android.view.LayoutInflater.rInflateChildren (LayoutInflater.java:828)

  at android.view.LayoutInflater.rInflate (LayoutInflater.java:873)

  at android.view.LayoutInflater.rInflateChildren (LayoutInflater.java:828)

  at android.view.LayoutInflater.inflate (LayoutInflater.java:525)

  at android.view.LayoutInflater.inflate (LayoutInflater.java:427)

  at package.Accueil.onCreateView (Accueil.java:75)

  at android.support.v4.app.Fragment.performCreateView (Fragment.java:1965)

  at android.support.v4.app.FragmentManagerImpl.moveToState (FragmentManager.java:1078)

  at android.support.v4.app.FragmentManagerImpl.moveToState (FragmentManager.java:1259)

  at android.support.v4.app.BackStackRecord.run (BackStackRecord.java:738)

  at android.support.v4.app.FragmentManagerImpl.execPendingActions (FragmentManager.java:1624)

  at android.support.v4.app.FragmentController.execPendingActions (FragmentController.java:330)

  at android.support.v4.app.FragmentActivity.onStart (FragmentActivity.java:547)

  at android.app.Instrumentation.callActivityOnStart (Instrumentation.java:1256)

  at android.app.Activity.performStart (Activity.java:6972)

  at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2937)

  at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:3045)

  at android.app.ActivityThread.-wrap14 (ActivityThread.java)

  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1642)

  at android.os.Handler.dispatchMessage (Handler.java:102)

  at android.os.Looper.loop (Looper.java:154)

  at android.app.ActivityThread.main (ActivityThread.java:6776)

  at java.lang.reflect.Method.invoke (Native Method)

  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1496)

  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1386)

The crash line : at package.Accueil.onCreateView (Accueil.java:75)

Is this one:

TextView textView = (TextView) getActivity().findViewById(R.id.main_toolbar_title);

I don't understand how the app can crash on this line. I did search on Google they talk about big file to load...

Here is all of my drawables:

The view:

I think the problem is with my drawables and the density of the images, I don't rteally understand this: I did a question about:

Understanding Drawables and Images sizes

I don't know if I have all screen sizes.

OutOfMemoryError is not possible with this line of code . Double check your production code and confirm the line number . — SpiritCrusher
– SpiritCrusher, Commented Feb 8, 2018 at 13:16
@duggu I have many images on this activity and big size images too — Ben
– Ben, Commented Feb 8, 2018 at 13:19
@ADM Ok Google Play Console showed this line (75) and the line is the TextView, how to know where it crashes — Ben
– Ben, Commented Feb 8, 2018 at 13:20

Konstantin Pribluda · Accepted Answer · 2018-02-08 13:20:06Z

1

OOME comes while instantiating your layout (especially images) - maybe there is some bad bitmap which is too big? Maybe your layout is too complex?

answered Feb 8, 2018 at 13:20

Konstantin Pribluda

12.3k1 gold badge33 silver badges38 bronze badges

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

8 Comments

Ben Over a year ago

Why the error is on this devices ? Can I simulate it with a virtual device ? I have many images, this is the image size or the weight ?

Konstantin Pribluda Over a year ago

Could be a lot of cauese - device has less memory than others, device uses one version of resource (because of screen resolution or whatever )which is buggy..... As for simulating on virtual device - it willl be difficult to recreate particular phone. Maybe you can get real one and debug?

Ben Over a year ago

So I can't know where it came from ? Can I do something ? Like pass images on tinypng to compress images ?

Konstantin Pribluda Over a year ago

It is definitely some image. Hard to telll which. DO you have dieeferent assets for different resolutions etc?

Konstantin Pribluda Over a year ago

Impossible to tell what exact cause is.

|

Clapa Lucian · Accepted Answer · 2018-02-08 15:25:38Z

1

OOM is not usually related to one place. Even though the crash is at at package.Accueil.onCreateView (Accueil.java:75) most likely it's not caused by that. IN my experience the OOM are caused by bigger images than needed.

If you are downloading images from some server use Glide to fetch it because it will keep in memory only the resized image that fits your view even if the actual image was way bigger before resize. Check this comparison between Glide and Picasso: https://inthecheesefactory.com/blog/get-to-know-glide-recommended-by-google/en

You might also check for memory leaks using LeakCanary but I would first start with images.

answered Feb 8, 2018 at 15:25

Clapa Lucian

7002 gold badges8 silver badges14 bronze badges

1 Comment

Ben Over a year ago

Okay so I did an edit with the view, I don't have a lot of big images on, but I think the problem is with the drawables..

Nick Fortescue · Accepted Answer · 2018-02-08 16:04:39Z

0

Your problem is when this line is executed, the platform creates your View heirarchy. You presumably have lots of big images in your view, so your App has to allocate a lot of memory to display all these big images. So now the solution comes down to how do you fix things. You have two options:

Have a design with fewer or smaller images
Make your images use less memory

I'd advise doing both. I can't advise you on improving the design. But for reducing sizes, this section in the documentation is a good guide. It is talking about network transfer, but will probably help in your APK too.

There is also some good advice here.

answered Feb 8, 2018 at 16:04

Nick Fortescue

13.9k1 gold badge33 silver badges39 bronze badges

1 Comment

Ben Over a year ago

Okay so I did an edit with the view, I don't have a lot of big images on, but I think the problem is with the drawables..

Collectives™ on Stack Overflow

Google Play Console crash reporting java.lang.OutOfMemoryError

3 Answers 3

8 Comments

1 Comment

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

8 Comments

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related