TransactionTooLargeException Android Origin: On your device Last updated 13 Oct 2026

android.os.TransactionTooLargeException: data parcel size x bytes

Too much data was put into a Bundle/Intent/saved state, exceeding the ~1 MB Binder transaction buffer.

Exact message you may see data parcel size!!! FAILED BINDER TRANSACTION !!!
Seen on: Android

Meaning

Large lists or bitmaps in Intent extras, Fragment arguments or onSaveInstanceState crash, often only when the app goes to background (“data parcel size … bytes”).

Common causes

  • Bitmaps or large lists in Intent extras/Bundles
  • Large data in onSaveInstanceState / SavedStateHandle
  • FragmentStatePagerAdapter saving many fragments

⚡ Quick fix

  1. Pass IDs, not data; load data from a repository
  2. Keep saved state small
  3. Use a file/DB/ViewModel for large data

Detailed fix by platform

Kotlin

  1. startActivity(Intent(this, DetailActivity::class.java).putExtra("itemId", item.id)) // not the whole object list

How to diagnose

  1. Size — Bundle contents (TooLargeTool library)
  2. Timing — On background/rotation?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

409 — HTTP 409 Conflict (HTTP)409Actions must be plain objects — Error: Actions must be plain objects. Instead, the actual type was: 'function'. (React)Actions must be plain…ANR — ANR: Application Not Responding (Input dispatching timed out) (Android)ANRError acquiring the state lock — Terraform: Error: Error acquiring the state lock — ConditionalCheckFailedException / state blob is already locked (Terraform)Error acquiring the s…IllegalStateException — java.lang.IllegalStateException (Java)IllegalStateExceptionMaximum update depth — Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. (React)Maximum update depthModifying state during view update — SwiftUI: Modifying state during view update, this will cause undefined behavior (iOS)Modifying state durin…non-serializable value — A non-serializable value was detected in the state / in an action, in the path (React)non-serializable valueTransacti…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.