untime xception-Could not read input channel

问题描述

Could not read input channel: 5 W HardwareRenderer: EGL error: EGL_BAD_SURFACE
05-04 00:05:07.413 2865 2865 W HardwareRenderer: Mountain View, we've had a problem here. Switching back to software rendering.
05-04 00:05:07.413 234 935 E BufferQueue: [Toast] dequeueBuffer: can't dequeue multiple buffers without setting the buffer count
05-04 00:05:07.413 2865 2865 E Surface : dequeueBuffer failed (Invalid argument)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: Could not lock surface
05-04 00:05:07.413 2865 2865 E ViewRootImpl: java.lang.IllegalArgumentException
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.view.Surface.nativeLockCanvas(Native Method)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.view.Surface.lockCanvas(Surface.java:254)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.view.ViewRootImpl.drawSoftware(ViewRootImpl.java:2431)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.view.ViewRootImpl.draw(ViewRootImpl.java:2405)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2249)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1879)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:996)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5602)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:762)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.view.Choreographer.doCallbacks(Choreographer.java:575)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.view.Choreographer.doFrame(Choreographer.java:545)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:748)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.os.Handler.handleCallback(Handler.java:733)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.os.Handler.dispatchMessage(Handler.java:95)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.os.Looper.loop(Looper.java:136)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at android.app.ActivityThread.main(ActivityThread.java:5119)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at java.lang.reflect.Method.invokeNative(Native Method)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at java.lang.reflect.Method.invoke(Method.java:515)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
05-04 00:05:07.413 2865 2865 E ViewRootImpl: at dalvik.system.NativeStart.main(Native Method)
05-04 00:05:07.413 911 926 D WindowManager: lid state 1, true
05-04 00:05:07.423 911 926 D WindowManager: lid state 1, true
05-04 00:05:07.433 911 926 I ActivityManager: Displayed com.android.contacts/.activities.ContactDetailActivity: +231ms
05-04 00:05:07.433 911 1184 V InputMethodManagerService: windowGainedFocus: android.os.BinderProxy@41c9f740 controlFlags=#104 softInputMode=#110 windowFlags=#1810100
05-04 00:05:07.433 911 926 I am_activity_launch_time: [0,1109596056,com.android.contacts/.activities.ContactDetailActivity,231,231]
05-04 00:05:07.443 2865 2865 E InputChannel-JNI: Error 24 dup channel fd 1014.
05-04 00:05:07.443 2865 2865 D AndroidRuntime: Shutting down VM
05-04 00:05:07.453 2865 2865 W dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x41650d58)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: FATAL EXCEPTION: main
05-04 00:05:07.453 2865 2865 E AndroidRuntime: Process: com.android.contacts, PID: 2865
05-04 00:05:07.453 2865 2865 E AndroidRuntime: java.lang.RuntimeException: Could not read input channel file descriptors from parcel.
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at android.view.InputChannel.nativeReadFromParcel(Native Method)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at android.view.InputChannel.readFromParcel(InputChannel.java:148)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at android.view.InputChannel$1.createFromParcel(InputChannel.java:39)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at android.view.InputChannel$1.createFromParcel(InputChannel.java:36)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at com.android.internal.view.InputBindResult.(InputBindResult.java:62)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at com.android.internal.view.InputBindResult$1.createFromParcel(InputBindResult.java:102)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at com.android.internal.view.InputBindResult$1.createFromParcel(InputBindResult.java:99)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at com.android.internal.view.IInputMethodManager$Stub$Proxy.windowGainedFocus(IInputMethodManager.java:713)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at android.view.inputmethod.InputMethodManager.startInputInner(InputMethodManager.java:1169)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at android.view.inputmethod.InputMethodManager.onWindowFocus(InputMethodManager.java:1376)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at android.view.ViewRootImpl$ViewRootHandler.handleMessage(ViewRootImpl.java:3141)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at android.os.Looper.loop(Looper.java:136)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5119)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at java.lang.reflect.Method.invokeNative(Native Method)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:515)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605)
05-04 00:05:07.453 2865 2865 E AndroidRuntime: at dalvik.system.NativeStart.main(Native Method)
05-04 00:05:07.453 911 926 D WindowManager: lid state 1, true
05-04 00:05:07.453 911 1326 W ActivityManager: Force finishing activity com.android.contacts/.activities.ContactDetailActivity
05-04 00:05:07.453 911 1326 D PowerManagerService: acquireWakeLockInternal: lock=1101082000, flags=0x1, tag="ActivityManager-Launch", ws=null, uid=1000, pid=911
05-04 00:05:07.453 911 1326 D PowerManagerService: updateWakeLockSummaryLocked: mWakefulness=Awake, mWakeLockSummary=0x23
05-04 00:05:07.453 911 1326 D PowerManagerService: newScreenState: 2
05-04 00:05:07.453 911 1326 D DisplayPowerController: requestPowerState: screenState=2, useProximitySensor=fals

时间： 2024-11-03 21:42:10

untime xception-Could not read input channel的相关文章

runtimeexception-Could not read input channel……

问题描述 Could not read input channel-- Could not read input channel file descriptors from parcel. 1.RemoteView中添加的图片太大了,超过40K会报这个异常 2.Intent传递的数据太大了超过1M也会报这个错误 3.FileDescripter太多而且没有关闭,looper太多没有quit. 4.试试在AndroidManefest.xml中对当前Activity配置configchange="

WCF后续之旅(2) 如何对Channel Layer进行扩展——创建自定义Channel

在上一篇文章中,我们通过一个直接借助BasicHttpBinding对象实现Client和Server端进行通信的例子,对WCF channel layer进行了一个大致上的介绍.由此引出了一些列通信相关的概念和对象,比如Channel,Output channel, Input channel,Request channel, Reply Channel,Duplex channel, Channel Shape,Channel manager,Channel factory, Channel

变形卷积核、可分离卷积？卷积神经网络中10大拍案叫绝的操作

CNN从2012年的AlexNet发展至今,科学家们发明出各种各样的CNN模型,一个比一个深,一个比一个准确,一个比一个轻量.我下面会对近几年一些具有变革性的工作进行简单盘点,从这些充满革新性的工作中探讨日后的CNN变革方向. 注:水平所限,下面的见解或许有偏差,望大牛指正.另外只介绍其中具有代表性的模型,一些著名的模型由于原理相同将不作介绍,若有遗漏也欢迎指出. 1. 卷积只能在同一组进行吗?-- Group convolution Group convolution 分组卷积,最早在Alex

变形卷积核、可分离卷积？卷积神经网络中十大拍案叫绝的操作。

从2012年的AlexNet发展至今,科学家们发明出各种各样的CNN模型,一个比一个深,一个比一个准确,一个比一个轻量.我下面会对近几年一些具有变革性的工作进行简单盘点,从这些充满革新性的工作中探讨日后的CNN变革方向. 注:水平所限,下面的见解或许有偏差,望大牛指正.另外只介绍其中具有代表性的模型,一些著名的模型由于原理相同将不作介绍,若有遗漏也欢迎指出. 一.卷积只能在同一组进行吗?-- Group convolution Group convolution 分组卷积,最早在AlexNet中

android出现闪退-android开发华为p6卡顿

问题描述 android开发华为p6卡顿开发的app在大部分手机上都挺流畅,但是在华为p6上特别卡顿,而且经常崩溃,在华为m7闪退解决方案如果有.so文件的话试试这个在build.gradle里面加上这个 android { .... defaultConfig { ... multiDexEnabled true ndk { abiFilters "armeabi" } } sourceSets { main { jniLibs.srcDirs = ['libs'] }

globalalloc、malloc和new的区别

GlobalAlloc 是为了与Win16兼容才保留的,在Win32下不要使用. 全局内存对象使用GlobalAlloc函数分配,在 Windows 3.X的时代,分配的内存可以有两种,全局的和局部的,例如GlobalAlloc和LocalAlloc.但在Win32的时代这些函数已经被废弃了,现在的内存只有一种就是虚存.在Win32中所有的进程所使用的内存区域是相互隔离的,每个进程都拥有自己的地址空间.而且系统使用了页面交换功能,就是利用磁盘空间来模拟RAM,在RAM中数据不使用时将会被交换

Java多线程：“JUC锁”04之公平锁(二)

概要前面一章,我们学习了"公平锁"获取锁的详细流程:这里,我们再来看看"公平锁 "释放锁的过程.内容包括: 参考代码释放公平锁(基于JDK1.7.0_40) "公平锁"的获取过程请参考"Java多线程系列--"JUC锁"03之公平锁 (一)",锁的使用示例请参考"Java多线程系列--"JUC锁"02之互斥锁 ReentrantLock". 注意: (01)

Unity3D中Coroutine的用法

unity3d开发中Coroutine到底是怎么用的? 昨天在测试的时候发生了很严重的当机事件,不管用什么Android的手机,在游玩过程中会不定时的无任何警示讯息自动跳出,从LogCat看讯息发现: 1.ERROR/InputDispatcher(284): channel '418b6698 path.to.our.app (server)' ~ Consumer closed input channel or an error occurred. events=0×8 2.ERROR/I

Apache Flink fault tolerance源码剖析(六)

上篇文章我们分析了基于检查点的用户状态的保存机制--状态终端.这篇文章我们来分析barrier(中文常译为栅栏或者屏障,为了避免引入名称争议,此处仍用英文表示).检查点的barrier是提供exactly once一致性保证的主要保证机制.这篇文章我们会就此展开分析. 这篇文章我们侧重于核心代码分析,原理我们在这个系列的第一篇文章<Flink数据流的Fault Tolerance机制> 一致性保证 Flink的一致性保证也依赖于检查点机制.在利用检查点进行恢复时,数据流会进行重放(replay