原文出處：http://blog.csdn.net/xxooyc/article/details/50162523，（部分修改）

bug描述

W/System.err: java.lang.RuntimeException: Package manager has died W/System.err: at android.app.ApplicationPackageManager.getPackageInfo(ApplicationPackageManager.java:122) W/System.err: at com.qq.googleplay.common.utils.AppUtil.isInstalled(AppUtil.java:73) W/System.err: at com.qq.googleplay.manager.DownloadManager.getDownLoadInfo(DownloadManager.java:182) W/System.err: at com.qq.googleplay.ui.fragment.HomeFragment$HomeAdapter$1.run(HomeFragment.java:179) W/System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112) W/System.err: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587) W/System.err: at java.lang.Thread.run(Thread.java:818)

出現bug的代碼

/*** 判斷包是否安裝** @param context* @param packageName* @return*/public static boolean isInstalled(Context context, String packageName) {PackageManager manager = context.getPackageManager();try {manager.getPackageInfo(packageName, PackageManager.GET_ACTIVITIES);return true;} catch (PackageManager.NameNotFoundException e) {return false;}}

bug分析

frameworks/base/core/java/Android/app/ApplicationPackageManager.java

@Override public PackageInfo getPackageInfo(String packageName, int flags) throws NameNotFoundException { try { PackageInfo pi = mPM.getPackageInfo(packageName, flags, mContext.getUserId()); if (pi != null) { return pi; } } catch (RemoteException e) { throw new RuntimeException("Package manager has died", e); } throw new NameNotFoundException(packageName); }

這是一個Binder調用，造成這個的原因是因為發生了RemoteException

Caused by: android.os.TransactionTooLargeException

W/System.err: Caused by: android.os.TransactionTooLargeException W/System.err: at android.os.BinderProxy.transactNative(Native Method) W/System.err: at android.os.BinderProxy.transact(Binder.java:507) W/System.err: at android.content.pm.IPackageManager$Stub$Proxy.getPackageInfo(IPackageManager.java:1806) W/System.err: at android.app.ApplicationPackageManager.getPackageInfo(ApplicationPackageManager.java:117)

frameworks/base/core/jni/android_util_Binder.cpp

case FAILED_TRANSACTION: ALOGE("!!! FAILED BINDER TRANSACTION !!!"); // TransactionTooLargeException is a checked exception, only throw from certain methods. // FIXME: Transaction too large is the most common reason for FAILED_TRANSACTION // but it is not the only one. The Binder driver can return BR_FAILED_REPLY // for other reasons also, such as if the transaction is malformed or // refers to an FD that has been closed. We should change the driver // to enable us to distinguish these cases in the future. jniThrowException(env, canThrowRemoteException ? "android/os/TransactionTooLargeException" : "java/lang/RuntimeException", NULL); break;

可以看出如果Binder的使用超出了一個進程的限制就會拋出TransactionTooLargeException這個異常。如果是其他原因造成Binder crash的話就會拋出RuntimeException。

那一個進程的Binder內存限制是多少？

frameworks/native/libs/binder/ProcessState.cpp：

#define BINDER_VM_SIZE ((1*1024*1024) - (4096 *2))

這便是一個進程中binder的大小，大約1M。

給Binder分配內存的代碼：

#if !defined(HAVE_WIN32_IPC) // mmap the binder, providing a chunk of virtual address space to receive transactions. mVMStart = mmap(0, BINDER_VM_SIZE, PROT_READ, MAP_PRIVATE | MAP_NORESERVE, mDriverFD, 0); if (mVMStart == MAP_FAILED) { // *sigh* ALOGE("Using /dev/binder failed: unable to mmap transaction memory.\n"); close(mDriverFD); mDriverFD = -1; }

通過上面的清理，知道了如果一個進程中使用的Binder內容超過了1M，就會crash.

而如果這時候恰巧在用getPackageManager()做事情，就會提示Package manager has died

可以事實真的是這樣的嗎？

寫了個demo來證明一下

public class MainActivity extends Activity { @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); test(); } private void test() { for (int i = 0; i < 2; i++) { new Thread() { @Override public void run() { int count = 0; List<PackageInfo> list = getPackageManager() .getInstalledPackages(10000); for (PackageInfo info : list) { if(count >=1000){ break; } try { PackageInfo pi = getPackageManager() .getPackageInfo(info.packageName, PackageManager.GET_ACTIVITIES); Log.e("yanchen", "yanchen threadid:"+Thread.currentThread().getId() + ",i:" + count++); } catch (NameNotFoundException e) { } } } }.start(); } } }

這個Demo就是同時創建兩個線程來進行Binder調用

運行打印的log

E/yanchen (21180): yanchen threadid:4097,i:271 E/yanchen (21180): yanchen threadid:4097,i:272 E/yanchen (21180): yanchen threadid:4097,i:273 E/yanchen (21180): yanchen threadid:4097,i:274 E/yanchen (21180): yanchen threadid:4097,i:275 E/yanchen (21180): yanchen threadid:4097,i:276

此時也如預期發生了Crash:

E/JavaBinder(31244): !!! FAILED BINDER TRANSACTION !!! E/AndroidRuntime(31244): FATAL EXCEPTION: Thread-4798 E/AndroidRuntime(31244): Process: com.example.testdl, PID: 31244 E/AndroidRuntime(31244): java.lang.RuntimeException: Package manager has died E/AndroidRuntime(31244): at android.app.ApplicationPackageManager.getPackageInfo(ApplicationPackageManager.java:155) E/AndroidRuntime(31244): at com.example.testdl.MainActivity$1.run(MainActivity.java:40) E/AndroidRuntime(31244): Caused by: android.os.TransactionTooLargeException E/AndroidRuntime(31244): at android.os.BinderProxy.transactNative(Native Method) E/AndroidRuntime(31244): at android.os.BinderProxy.transact(Binder.java:496) E/AndroidRuntime(31244): at android.content.pm.IPackageManager$Stub$Proxy.getPackageInfo(IPackageManager.java:2208) E/AndroidRuntime(31244): at android.app.ApplicationPackageManager.getPackageInfo(ApplicationPackageManager.java:150) E/AndroidRuntime(31244): ... 1 more D/EnterpriseDeviceManagerService( 3021): isMana

解決方式

其實只要避免多個線程同時來調用Binder就可以了，畢竟一個線程用了會釋放，所以理論上是很難發生的。

修改后的Demo

synchronized(MainActivity.class){ PackageInfo pi = getPackageManager() .getPackageInfo(info.packageName,PackageManager.GET_ACTIVITIES); }

再次運行就不會Crash了

總結

以上是生活随笔為你收集整理的RuntimeException: Package manager has died的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。