Android.os.DeadObjectException memory near R0: Exception handling Consumer closed input channel or an error occurred. events=0x9

Original address: http://www.cnblogs.com/wanqieddy/p/3495338.html

Android.os.DeadObjectException memory near R0: Exception handling

Android.os.DeadObjectException

08-15 14:39:32.486:w/system.err (1767): at Android.os.BinderProxy.transact (Native Method)

08-15 14:39:32.486:i/activitymanager (1767): Process com.my.test (PID 25619) has died.

08-15 14:39:32.486:w/activitymanager (1767): Force removing Activityrecord{42afefe8 com.my.tes/. MYCMGE}: App died, no saved state

08-15 14:39:32.486:w/windowmanager (1767): Force-removing child win window{441d3f70 Popupwindow:4299edc8 Paused=false} From container window{42ae1b88 com.my.tes/com.my.tes.mycmge Paused=false}

08-15 14:39:32.491:w/system.err (1767): at Android.view.iwindow$stub$proxy.offsetwindowforkeyguard (IWindow.java : 471)

08-15 14:39:32.491:w/inputdispatcher (1767): Channel ' 441da238 com.my.tes/com.my.tes.mycmge (server) ' ~ Consumer closed  Input channel or an error occurred. events=0x9

08-15 14:39:32.491:e/inputdispatcher (1767): Channel ' 441da238 com.my.tes/com.my.tes.mycmge (server) ' ~ Channel is Unrecoverably broken and would be disposed!

08-15 14:39:32.491:w/system.err (1767): at Com.android.server.wm.WindowStateAnimator.destroySurfaceLocked ( windowstateanimator.java:803)

08-15 14:39:32.491:w/system.err (1767): at com.android.server.wm.WindowState.removeLocked (windowstate.java:832)

08-15 14:39:32.491:w/system.err (1767): at Com.android.server.wm.WindowManagerService.removeWindowInnerLocked ( windowmanagerservice.java:2522)

08-15 14:39:32.491:w/system.err (1767): at Com.android.server.wm.WindowManagerService.removeWindowInnerLocked ( windowmanagerservice.java:2506)

08-15 14:39:32.491:d/zygote (1550): Process 25619 terminated by signal (11)

08-15 14:39:32.491:w/system.err (1767): at Com.android.server.wm.WindowManagerService.removeWindowLocked ( windowmanagerservice.java:2484)

08-15 14:39:32.491:w/system.err (1767): at Com.android.server.wm.windowstate$deathrecipient.binderdied ( windowstate.java:869)

08-15 14:39:32.491:w/system.err (1767): at Android.os.BinderProxy.sendDeathNotice (binder.java:449)

08-15 14:39:32.491:w/system.err (1767): at Dalvik.system.NativeStart.run (Native Method)

08-15 14:39:32.491:i/akmd2 (1767): ak8975/b for Android end.

08-15 14:39:32.491:d/akmd2 (1767): Akmd2:compass Closed.

08-15 14:39:32.491:d/sensors (1767): Akm:setdelay (): Handle 1, delay 20000000 NS.

08-15 14:39:32.496:d/akmd2 (1767): Acc_thread_main:update Delay_ms to 66.

In this case, my test will only happen to Meizu 2 phone, the following article from the Code layer debugging has been changed,

http://blog.csdn.net/casun_li/article/details/8966565

I am using someone else's SDK so there is no way to change the source, so help Daniel, using the following methods to easily solve the

<application

Android:hardwareaccelerated= "false" .....

That is, add a android:hardwareaccelerated= "false" to the application tag (Disable hardware acceleration)

So the problem is solved,

At the beginning I was added to the corresponding activity, the label inside, the results found that the first time can be run perfect for some time and this problem will occur,

Changed the application,android:hardwareaccelerated= "false" so it was good,

The problem is really sore,,, but hopefully there's a good solution. Someone to share, hardware acceleration issues that affect game performance