5

I am working on the production app. I am receiving the exception in Crashlytics. I don't have a clue where is happening because it is not pointing any activity. Just I am getting an error like this.

Caused by android.os.TransactionTooLargeException: data parcel size 5971992 bytes
   at android.os.BinderProxy.transactNative(BinderProxy.java)
   at android.os.BinderProxy.transact(BinderProxy.java:1179)
   at android.app.IActivityManager$Stub$Proxy.activityStopped(IActivityManager.java:3969)
   at android.app.servertransaction.PendingTransactionActions$StopInfo.run(PendingTransactionActions.java:144)
   at android.os.Handler.handleCallback(Handler.java:873)
   at android.os.Handler.dispatchMessage(Handler.java:99)
   at android.os.Looper.loop(Looper.java:193)
   at android.app.ActivityThread.main(ActivityThread.java:6898)
   at java.lang.reflect.Method.invoke(Method.java)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:537)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

Is there any tool/library to detect this issue

I checked this link also What to do on TransactionTooLargeException

I tried this tool https://github.com/guardian/toolargetoo it's not helpful for me.Can you kindly share your ideas

Ramesh sambu
  • 3,577
  • 2
  • 24
  • 39
  • 1
    are you passing large set of data via intent to another activity? can you check that. very difficult to tell whats happening without more details. – Raghunandan Jan 13 '20 at 11:37
  • No bro I am not passing large data like POJO. Just passing key-value pairs – Ramesh sambu Jan 13 '20 at 11:40
  • you need to debug yourself. the details provided here are not enough for anyone to assume whats happening. – Raghunandan Jan 13 '20 at 11:42
  • Yes even while testing in staging mode I am not getting errors in the application, In production, I am receiving this bug even which screen not able to find bro – Ramesh sambu Jan 13 '20 at 11:45
  • 1
    In addition to Intents, have a look at your activities and fragments if they'd be storing potentially large data in an instance state parcel. – laalto Jan 13 '20 at 11:48
  • Agreed on the instance state -- from this particular stack trace, that seems like the most likely culprit. So, for example, do not put a `Bitmap` into the saved instance state `Bundle`. – CommonsWare Jan 13 '20 at 12:13
  • Thank you all I will try to debug all places – Ramesh sambu Jan 13 '20 at 12:18
  • @CommonsWare Thanks man I got my answer from your comment. It was due to putting parceable bitmap into the saved instance state Bundle . – Umair Iqbal Sep 24 '20 at 08:17

0 Answers0