Activity之间使用intent传递大量数据问题

bug

问题：设 A -> B ,当传递数据量过大，会导致B无法启动。现象即启动失败，activityB的oncreate()都不会执行。

会提示 TransactionTooLargeException 异常

TransactionTooLargeException 官网解释

The Binder transaction failed because it was too large.
During a remote procedure call, the arguments and the return value of the call are transferred as Parcel objects stored in the Binder transaction buffer. If the arguments or the return value are too large to fit in the transaction buffer, then the call will fail and TransactionTooLargeException will be thrown.
The Binder transaction buffer has a limited fixed size, currently 1Mb, which is shared by all transactions in progress for the process. Consequently this exception can be thrown when there are many transactions in progress even when most of the individual transactions are of moderate size.
// 一般进程中有 1MB Binder transaction buffer 共享传递的数据，大小超过这个buffer，则会抛出该异常。
There are two possible outcomes when a remote procedure call throws TransactionTooLargeException. Either the client was unable to send its request to the service (most likely if the arguments were too large to fit in the transaction buffer), or the service was unable to send its response back to the client (most likely if the return value was too large to fit in the transaction buffer). It is not possible to tell which of these outcomes actually occurred. The client should assume that a partial failure occurred.
// 这段话可以 结合使用AIDL或Messenger的场景来理解（因为都是通过Binder对象传值）
// 2种可能结果
//1：客户端传递的数据大于the transaction buffer
//2：服务端返回的数据大于the transaction buffer
The key to avoiding TransactionTooLargeException is to keep all transactions relatively small. Try to minimize the amount of memory needed to create a Parcel for the arguments and the return value of the remote procedure call. Avoid transferring huge arrays of strings or large bitmaps. If possible, try to break up big requests into smaller pieces.
// 避免的建议： 保证所有传递数据尽量小
// 1. 使用 Parcel
// 2. 避免传递大数组，字符串集，位图
// 3. 大请求压缩为更小块
If you are implementing a service, it may help to impose size or complexity contraints on the queries that clients can perform. For example, if the result set could become large, then don't allow the client to request more than a few records at a time. Alternately, instead of returning all of the available data all at once, return the essential information first and make the client ask for additional information later as needed.
// 实现service的建议

Binder （引自Android开发艺术探索）

• Binder是Android中的一个类，实现了IBinder接口。
• IPC的角度：Binder是Android中的一种跨进程通信方式，还可以被理解为一种虚拟的物理设备，它的设备驱动是/dev/binder,该通信方式在Linux中没有。
• Android Framework角度：Binder是ServiceManager连接各种Manager（ActivityManager,WindowManger等）和相应ManagerService的桥梁。
• 应用层角度：Binder是客户端和服务器进行通信的媒介，当bindService时，服务端会返回一个包含了服务端业务调用的Binder对象（如基于AIDL的服务或Messenger）。

解决思路：

-

处理例子：

1.
when i am dealing with the WebViewin my app,it happens.i think it's related to 'addView' and UI resources. in my app ,i add some code in WebViewActivity like this below,it runs ok:

@Override
protected void onDestroy() {
    if (mWebView != null) {
        ((ViewGroup) mWebView.getParent()).removeView(mWebView);  
        mWebView.removeAllViews();  
        mWebView.destroy();
    }
    super.onDestroy();
}

2.
There isn't one specific cause of this problem.For me, in my Fragment class I was doing this:

public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
    super.onCreateView(inflater, container, savedInstanceState);
    View rootView = inflater.inflate(R.layout.snacks_layout, container); //<-- notice the absence of the false argument
    return rootView;
}

instead of this:

View rootView = inflater.inflate(R.layout.softs_layout, container, false);

http://www.tuicool.com/articles/QBBvy22
http://stackoverflow.com/questions/11451393/what-to-do-on-transactiontoolargeexception
http://androiddoc.qiniudn.com/reference/android/os/TransactionTooLargeException.html