- android - RelativeLayout 背景可绘制重叠内容
- android - 如何链接 cpufeatures lib 以获取 native android 库?
- java - OnItemClickListener 不起作用,但 OnLongItemClickListener 在自定义 ListView 中起作用
- java - Android 文件转字符串
有时,我的应用程序被卡住,然后崩溃。
我阅读了系统日志,并在系统日志的最后几行中看到我的 Activity 出现一些“WIN DEATH”错误。
谁能告诉我原因并告诉我解决方法?
非常感谢!
这是系统日志:
08-17 08:34:00.091 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.101 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.101 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.111 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.121 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.131 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.131 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.141 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.151 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.151 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.161 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.171 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.171 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.181 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.191 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.191 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.211 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:01.692 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.dell.launcher/.Launcher }
08-17 08:34:01.711 D/StatusBar( 149): nAnimY < mStatusBarView.getHeight()
08-17 08:34:01.731 W/InputManagerService( 149): Ignoring hideSoftInput of: com.android.internal.view.IInputMethodClient$Stub$Proxy@46f51200
08-17 08:34:01.751 I/ActivityManager( 149): No longer want com.android.vending (pid 724): hidden #16
08-17 08:34:03.141 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.browser/.BrowserActivity bnds=[289,313][375,390] }
08-17 08:34:03.521 W/InputManagerService( 149): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@46ee34f8 (uid=10006 pid=893)
08-17 08:34:03.521 W/InputManagerService( 149): Client not active, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@46f02ef0
08-17 08:34:08.301 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.VIEW dat=http://vnexpress.net/ flg=0x10000000 cmp=com.android.browser/.BrowserActivity (has extras) }
08-17 08:34:43.361 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.VIEW cat=[android.intent.category.BROWSABLE] dat=http://vnexpress.net/gl/the-gioi/phan-tich/2012/08/trung-quoc-se-bi-co-lap-neu-bat-hop-tac-ve-bien-dong-1/ cmp=com.android.browser/.BrowserActivity }
08-17 08:34:43.911 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.VIEW cat=[android.intent.category.BROWSABLE] dat=http://vnexpress.net/gl/the-gioi/phan-tich/2012/08/trung-quoc-se-bi-co-lap-neu-bat-hop-tac-ve-bien-dong-1/ cmp=com.android.browser/.BrowserActivity }
08-17 08:35:06.701 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.dell.launcher/.Launcher }
08-17 08:35:06.711 D/StatusBar( 149): nAnimY < mStatusBarView.getHeight()
08-17 08:35:06.751 W/InputManagerService( 149): Ignoring hideSoftInput of: com.android.internal.view.IInputMethodClient$Stub$Proxy@47017a48
08-17 08:35:10.341 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=i3.mobile1/i3.mobile.dvrremote.screen.WelcomeScreen }
08-17 08:35:10.361 D/StatusBar( 149): nAnimY < mStatusBarView.getHeight()
08-17 08:35:16.144 W/WindowManager( 149): Key dispatching timed out sending to i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen
08-17 08:35:16.144 W/WindowManager( 149): Previous dispatch state: null
08-17 08:35:16.144 W/WindowManager( 149): Current dispatch state: {{null to Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=false} @ 1345167316145 lw=Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=false} lb=android.os.BinderProxy@46e87e58 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=false}}}
08-17 08:35:16.421 E/ActivityManager( 149): ANR in i3.mobile1i3.mobile1(pid: 941) (i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen)
08-17 08:35:16.421 E/ActivityManager( 149): Reason: keyDispatchingTimedOut
08-17 08:35:16.421 E/ActivityManager( 149): Load: 5.13 / 5.05 / 3.69
08-17 08:35:16.421 E/ActivityManager( 149): CPU usage from 5531ms to 13ms ago:
08-17 08:35:16.421 E/ActivityManager( 149): system_server: 2% = 1% user + 1% kernel / faults: 35 minor 19 major
08-17 08:35:16.421 E/ActivityManager( 149): android.browser: 1% = 0% user + 0% kernel / faults: 21 minor 2 major
08-17 08:35:16.421 E/ActivityManager( 149): m.android.phone: 0% = 0% user + 0% kernel / faults: 48 minor 2 major
08-17 08:35:16.421 E/ActivityManager( 149): e.process.gapps: 0% = 0% user + 0% kernel / faults: 21 minor 1 major
08-17 08:35:16.421 E/ActivityManager( 149): m.dell.launcher: 0% = 0% user + 0% kernel / faults: 20 minor
08-17 08:35:16.421 E/ActivityManager( 149): events/0: 0% = 0% user + 0% kernel
08-17 08:35:16.421 E/ActivityManager( 149): auo_touchscreen: 0% = 0% user + 0% kernel
08-17 08:35:16.421 E/ActivityManager( 149): d.process.acore: 0% = 0% user + 0% kernel / faults: 23 minor
08-17 08:35:16.421 E/ActivityManager( 149): m.android.music: 0% = 0% user + 0% kernel / faults: 219 minor 1 major
08-17 08:35:16.421 E/ActivityManager( 149): com.oem.lota: 0% = 0% user + 0% kernel / faults: 53 minor 1 major
08-17 08:35:16.421 E/ActivityManager( 149): ndroid.dellsync: 0% = 0% user + 0% kernel / faults: 43 minor
08-17 08:35:16.421 E/ActivityManager( 149): cpanda.aquapets: 0% = 0% user + 0% kernel / faults: 61 minor
08-17 08:35:16.421 E/ActivityManager( 149): ndroid.settings: 0% = 0% user + 0% kernel / faults: 14 minor
08-17 08:35:16.421 E/ActivityManager( 149): lite.dellstreak: 0% = 0% user + 0% kernel / faults: 25 minor
08-17 08:35:16.421 E/ActivityManager( 149): d.photos:Remote: 0% = 0% user + 0% kernel / faults: 17 minor
08-17 08:35:16.421 E/ActivityManager( 149): equicksearchbox: 0% = 0% user + 0% kernel / faults: 22 minor
08-17 08:35:16.421 E/ActivityManager( 149): TOTAL: 7% = 3% user + 3% kernel + 0% iowait
08-17 08:35:16.551 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:16.881 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:20.351 W/ActivityManager( 149): Launch timeout has expired, giving up wake lock!
08-17 08:35:20.361 W/ActivityManager( 149): Activity idle timeout for HistoryRecord{46e20d08 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen}
08-17 08:35:48.398 W/WindowManager( 149): Key dispatching timed out sending to i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen
08-17 08:35:48.398 W/WindowManager( 149): Previous dispatch state: null
08-17 08:35:48.398 W/WindowManager( 149): Current dispatch state: {{null to Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=false} @ 1345167348400 lw=Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=false} lb=android.os.BinderProxy@46e87e58 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=false}}}
08-17 08:35:48.841 E/ActivityManager( 149): ANR in i3.mobile1i3.mobile1(pid: 941) (i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen)
08-17 08:35:48.841 E/ActivityManager( 149): Reason: keyDispatchingTimedOut
08-17 08:35:48.841 E/ActivityManager( 149): Load: 5.28 / 5.11 / 3.76
08-17 08:35:48.841 E/ActivityManager( 149): CPU usage from 32415ms to 58ms ago:
08-17 08:35:48.841 E/ActivityManager( 149): system_server: 6% = 4% user + 1% kernel / faults: 840 minor 1 major
08-17 08:35:48.841 E/ActivityManager( 149): android.browser: 1% = 1% user + 0% kernel / faults: 109 minor
08-17 08:35:48.841 E/ActivityManager( 149): .oem.logservice: 1% = 1% user + 0% kernel / faults: 1378 minor
08-17 08:35:48.841 E/ActivityManager( 149): m.dell.launcher: 0% = 0% user + 0% kernel / faults: 74 minor
08-17 08:35:48.841 E/ActivityManager( 149): ndroid.settings: 0% = 0% user + 0% kernel / faults: 72 minor
08-17 08:35:48.841 E/ActivityManager( 149): mmcqd: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): sensors_daemon: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): e.process.gapps: 0% = 0% user + 0% kernel / faults: 34 minor
08-17 08:35:48.841 E/ActivityManager( 149): mmcqd: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): cpanda.aquapets: 0% = 0% user + 0% kernel / faults: 7 minor
08-17 08:35:48.841 E/ActivityManager( 149): kswapd0: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): d.process.acore: 0% = 0% user + 0% kernel / faults: 42 minor
08-17 08:35:48.841 E/ActivityManager( 149): events/0: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): kjournald: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): ksdioirqd/mmc1: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): oid.inputmethod: 0% = 0% user + 0% kernel / faults: 25 minor 1 major
08-17 08:35:48.841 E/ActivityManager( 149): m.android.phone: 0% = 0% user + 0% kernel / faults: 1 minor
08-17 08:35:48.841 E/ActivityManager( 149): equicksearchbox: 0% = 0% user + 0% kernel / faults: 1 minor
08-17 08:35:48.841 E/ActivityManager( 149): auo_touchscreen: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): wpa_supplicant: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): viders.calendar: 0% = 0% user + 0% kernel / faults: 35 minor
08-17 08:35:48.841 E/ActivityManager( 149): d.process.media: 0% = 0% user + 0% kernel / faults: 18 minor
08-17 08:35:48.841 E/ActivityManager( 149): m.android.music: 0% = 0% user + 0% kernel / faults: 1 minor
08-17 08:35:48.841 E/ActivityManager( 149): ndroid.dellsync: 0% = 0% user + 0% kernel / faults: 1 minor
08-17 08:35:48.841 E/ActivityManager( 149): .packagechecker: 0% = 0% user + 0% kernel / faults: 20 minor
08-17 08:35:48.841 E/ActivityManager( 149): com.netgate: 0% = 0% user + 0% kernel / faults: 273 minor
08-17 08:35:48.841 E/ActivityManager( 149): .cooliris.media: 0% = 0% user + 0% kernel / faults: 25 minor
08-17 08:35:48.841 E/ActivityManager( 149): lite.dellstreak: 0% = 0% user + 0% kernel / faults: 1 minor
08-17 08:35:48.841 E/ActivityManager( 149): ogle.android.gm: 0% = 0% user + 0% kernel / faults: 30 minor 1 major
08-17 08:35:48.841 E/ActivityManager( 149): d.apps.uploader: 0% = 0% user + 0% kernel / faults: 17 minor
08-17 08:35:48.841 E/ActivityManager( 149): d.photos:Remote: 0% = 0% user + 0% kernel / faults: 1 minor
08-17 08:35:48.841 E/ActivityManager( 149): o.android.oemec: 0% = 0% user + 0% kernel / faults: 15 minor
08-17 08:35:48.841 E/ActivityManager( 149): i3.mobile1: 0% = 0% user + 0% kernel / faults: 16 minor 1 major
08-17 08:35:48.841 E/ActivityManager( 149): TOTAL: 32% = 11% user + 8% kernel + 12% iowait + 0% irq + 0% softirq
08-17 08:35:48.871 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:48.901 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:48.901 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:48.901 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:48.901 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:48.901 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:48.901 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:49.392 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:51.681 W/ActivityManager( 149): Force finishing activity i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen
08-17 08:35:51.681 I/ActivityManager( 149): Killing i3.mobile1 (pid=941): user's request
08-17 08:35:51.701 I/WindowManager( 149): WIN DEATH: Window{46e6fdb0 i3.mobile1/i3.mobile.dvrremote.screen.WelcomeScreen paused=false}
08-17 08:35:51.711 I/ActivityManager( 149): Process i3.mobile1 (pid 941) has died.
08-17 08:35:51.721 I/WindowManager( 149): WIN DEATH: Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=true}
08-17 08:35:51.721 I/ActivityManager( 149): Start proc i3.mobile1 for activity i3.mobile1/i3.mobile.dvrremote.screen.WelcomeScreen: pid=1119 uid=10106 gids={1015, 3003}
谢谢!
最佳答案
您的应用可能由于 ANR(应用程序无响应)而被终止。当您在 UI 线程中进行一些硬处理时,可能会发生这种情况。您可以在此处阅读更多信息:http://developer.android.com/guide/practices/responsiveness.html
只有一种解决方案:将所有繁重的工作转移到后台线程中,以便 UI 线程保持响应。
关于android - Android 中的 WIN DEATH 错误?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/13009499/
我正在尝试设置 RabbitMQ 以根据死亡原因通过死信交换路由消息(“x-death.reason”或“x-first-death-reason”都可以)。 我的理解是,当消息被发送到 DLX 时,
我一直在阅读关于在 Windows XP 和 Windows Server 2003 上针对 GDI+ 的旧漏洞利用。我正在做的一个项目被称为死亡 JPEG。 漏洞利用在以下链接中有很好的解释: ht
所以我是 C++ 的新手,我目前正在为一项任务开发一个“死亡之战”游戏,但我被卡住了。 基本上,作为玩家,您可以使用每种武器一定次数:Canon 3 次,Grenade 4 次。步枪是无限的。 当我使
我从 logcat 得到以下语句,就在一些成功的日志语句表明我的应用程序运行正常(统计输出等)之后: I/WindowState( 425): WIN DEATH: Window{4244e028
可能每个人在开发过程中都至少遇到过一次这个问题: while(/*some condition here that somehow never will be false*/) { ...
我很确定自己不仅是注意到PHP上的简单解析错误(如果存在于非常嵌套的场景中)的人(例如,引用另一个对象实例的对象实例引用了另一个解析错误很小的对象实例) ,它们全部被自动加载)可以使PHP永久挂起,而
我正在尝试使用批量加载器功能将大小适中的 csv 文件上传到 Google 应用引擎,但它似乎在中途死亡,结果如下: [INFO ] Logging to bulkloader-log-2011
我想将“死刑方法”与遗传算法文献中提出的其他惩罚方法进行比较。 我用的是R软件,所以需要写这些惩罚方法的代码。我发现了很多困难,因为我不了解关于死刑函数的一件事:我必须如何处理不可行的后代,因为人口规
关闭。这个问题是off-topic .它目前不接受答案。 想改进这个问题吗? Update the question所以它是on-topic用于堆栈溢出。 关闭 11 年前。 Improve thi
我正在寻找最合适的类作为从我的 Activity 调用的 AsyncTasks 的调度程序。 我认为它可能是其中之一: 应用程序的子类; 服务的子类; 我自己的静态 东西。 至于我 - 实现第三个选择
Epic游戏《《死神来了(Death Coming)》是一款呆萌像素风格的非线性解谜游戏 目前在Epic商城上限时免费 大家想玩的可以点击下方链接 添加游戏进入账号内然后下载玩耍 下载地址:
我正在尝试找到一种方法来模拟set -e在函数中的行为,但仅在该函数的范围内。 基本上,我想要一个函数,如果有任何简单的命令将触发set -e,它将返回1的上一级。目的是将有风险的工作集隔离为功能,以
我在 Android 1.5 模拟器(在 OS X 下运行)上遇到随机崩溃(尽管它们总是同时发生)。代码是针对 1.5 API 构建的,在其他版本上运行良好。应用程序在 HTC Hero 上执行相同操
我用cocos2d-x开发了一个游戏。我试着在android下编译它。前三个场景很好 - 但当我添加最后一个功能时,应用程序开始在随机时间和随机场景中关闭。 相关日志如下: 04-18 15:30:5
我正在查看 https://developer.android.com/topic/libraries/architecture/saving-states .它提到“系统启动的进程死亡”。它到底是什
我有一个启动服务的 Activity 。 在我的 Activity 中: startService(new Intent(this, MyService.class)); 在我的服务中,onStart
我知道这听起来是个懒惰的问题..但我真的不知道这种情况是如何发生的,我在谷歌上也找不到太多相关信息。 背景: 这是一个带有 IPC 的应用程序:我有一个在单独进程中运行的服务。有时,服务被杀死了……但
有时,我的应用程序被卡住,然后崩溃。 我阅读了系统日志,并在系统日志的最后几行中看到我的 Activity 出现一些“WIN DEATH”错误。 谁能告诉我原因并告诉我解决方法? 非常感谢! 这是系统
我有一个运行 Yii 应用程序的暂存服务器,现在显示“白屏死机”。我看不到任何东西被输出到屏幕上(甚至在“查看源代码”时看不到源代码),相同的代码在本地运行没有任何问题。 谁能推荐一个在 Yii 应用
据说 "static methods are death to testability" 。如果是这样,下面的可行替代模式是什么? class User { private $phone,
我是一名优秀的程序员,十分优秀!