DialogFragment.onStart触发android.os.TransactionTooLargeException异常求助

Hey there, let's break down why you're hitting this TransactionTooLargeException even though you're only passing two integers to your DialogFragment. The Binder 1MB limit isn't just about the arguments you explicitly pass—here are the most likely culprits to investigate:

1. Fragment state saving is carrying large hidden data #

Even if your newInstance method only passes two ints, your VideoEndDialog might be holding onto large objects that get serialized when the system saves the fragment's state. For example:

• A reference to a large Bitmap (like a video thumbnail or background image) stored as a member variable
• A big collection (e.g., List, Map) of video-related data cached in the fragment
• Unreleased resources like video frame buffers or media metadata

When the system calls onSaveInstanceState, these objects get bundled into the transaction, pushing it over the 1MB limit. Check your fragment's code for any large objects that aren't being cleared in onDestroyView or onDestroy.

2. Your Dialog's view hierarchy is too heavy #

The exception stack traces back to Dialog.show(), which means the issue might be with the view data being sent to the WindowManager. If your Dialog's layout has:

• Deeply nested view groups (like multiple layers of LinearLayout or RelativeLayout)
• Large drawables (high-resolution background images, complex vector assets)
• Custom views that store large amounts of data (e.g., a custom progress bar with cached animation frames)

All of these view-related details get serialized and passed via Binder when adding the Dialog's window. Even small elements can add up to exceed the limit. Try simplifying your layout, compressing images, or reducing nested layers.

3. Cumulative Binder transaction size from the app's navigation stack #

Binder transactions are cumulative—this Dialog's transaction might be stacking on top of other large transactions from earlier in your app's flow. For example:

• A previous Fragment or Activity passed a large Bundle with heavy data (like a list of video files)
• The FragmentManager's back stack holds multiple Fragments with saved state data that adds up
• System-level transactions (like configuration changes) are running in parallel and sharing the Binder limit

Check if you're passing large data between screens before showing this Dialog, or if you can clean up unused Fragments from the back stack to reduce the total transaction size.

4. Dialog window properties carry hidden large data #

Your Dialog's window configuration might be contributing to the transaction size without you realizing it:

• A custom WindowManager.LayoutParams that includes large extra data
• A Theme referencing large resources (like a full-screen background drawable)
• Unnecessary window flags or insets that carry additional serialized data

Try testing with a minimal default theme for the Dialog to see if the exception goes away, which would point to a theme-related issue.

Quick Debugging Tips #

• Enable StrictMode to log large Binder transactions early:

  // Add this to your Application's onCreate()
  StrictMode.setVmPolicy(new StrictMode.VmPolicy.Builder()
          .detectLargeHeap()
          .penaltyLog()
          .build());
  StrictMode.setThreadPolicy(new StrictMode.ThreadPolicy.Builder()
          .detectCustomSlowCalls()
          .penaltyLog()
          .build());
  

• Use adb shell dumpsys activity service StrictMode to pull detailed logs of large transactions and pinpoint which part of your app is sending excessive data.

内容的提问来源于stack exchange，提问作者Lyn