Hi, in one old application for Android, through the firebase system, claims began to arrive with an error, which I can’t achieve either on real or virtual devices for a month, this error comes strictly once a day at 8 pm in Kiev, but perhaps it’s so service sends.

As I understand it, this is due to the fact that I have a bunch of simultaneously displayed pictures in the application itself, and thus the memory runs out, as there was such a problem before, but I didn’t have any reports on it for a very long time, just as I rummaged in Google, it seemed like corrected her

The firebase report also states that only 1 person is affected, that is, I understand that he or he has a specific device, or he is the one who actively uses the application.

I have already tried everything that I could understand from the first pages of Google, but as I see it did not work, I really hope that someone will be able to tell where to dig, or how to achieve the same error with myself!

In the file: ViewRootImpl.java

The error sink itself:

java.lang.RuntimeException: Adding window failed at android.view.ViewRootImpl.setView (ViewRootImpl.java:746) at android.view.WindowManagerGlobal.addView (WindowManagerGlobal.java around78) at android.view.WindowManagerImpl.daddadd java: 69) at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3064) at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2394) at android.app.ActivityThread.access $ 900 (ActivityThread.java:169) at android.app.ActivityThread $ H.handleMessage (ActivityThread.java:1277) at android.os.Handler.dispatchMessage (Handler.java:102) at android.os.Looper.loop (Looper.java:136) at android. app.ActivityThread.main (ActivityThread.java:5479) at java.lang.reflect.Method.invokeNative (Method.java) at java.lang.reflect.Method.invoke (Method.java ind15) at com.android.internal .os.ZygoteInit $ MethodAndArgsCaller.run (ZygoteInit.java:1283) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1099) at dalvik.system.NativeStart.main (NativeS tart.java) Caused by: android.os.TransactionTooLargeException: at android.os.BinderProxy.transact (Binder.java) at android.view.IWindowSession $ Stub $ Proxy.addToDisplay (IWindowSession.java:710) at android.view. ViewRootImpl.setView (ViewRootImpl.java:735) at android.view.WindowManagerGlobal.addView (WindowManagerGlobal.java:278) at android.view.WindowManagerImpl.addView (WindowManagerImpl.java:69) at android.app.Antl.jlAjll.addView (WindowManagerImpl.java:69) at android.app.Antl.jl.jl.adl.a.l. .java: 3064) at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2394) at android.app.ActivityThread.access $ 900 (ActivityThread.java:169) at android.app.ActivityThread $ H.handleMessage (ActivityThread.java : 1277) at android.os.Handler.dispatchMessage (Handler.java:102) at android.os.Looper.loop (Looper.java:136) at android.app.ActivityThread.main (ActivityThread.java:5479) at java .lang.reflect.Method.invokeNative (Method.java) at java.lang.reflect.Method.invoke (Method.java-515) at com.android.internal.os.ZygoteInit $ MethodAndA rgsCaller.run (ZygoteInit.java:1283) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1099) at dalvik.system.NativeStart.main (NativeStart.java)

Thank!

    1 answer 1

    According to this response to en-SO TransactionTooLargeException may indeed be caused by a lack of memory.

    Treat can reduce the amount of information transferred between parts of the application. For example, not transferring a lot of pictures between activites through the Bundle . Other options are on the link at the beginning of the answer.

    • one
      It will be logical to try to catch the error by running the application on the virtual machine and allocate little memory to it. - Xoxole
    • Xoxole> I tried it, it did not work out, it just slows down and everything ... YuriySPb> is it possible that the old activities are not unloaded from memory and thus memory is clogged? - Andrey Shpileva