android.win论坛,Android中的WIN DEATH错误？

最新推荐文章于 2022-05-26 14:48:07 发布
最新推荐文章于 2022-05-26 14:48:07 发布
阅读量805 收藏
点赞数
文章标签： android.win论坛

有时,我的应用程序被冻结,然后崩溃.

我读了系统日志,在系统日志的最后几行,我在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}

谢谢！

无我的舞者
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
android 出现WIN DEATH 报出android.os.DeadObjectException
ifangler的专栏
10-09 2万+
今天遇到一个神奇的bug，app在4.4以下平台表现良好，在4.
android Win death的问题-1
热门推荐
u010538031的专栏
05-15 1万+
今天在修改安全登录的代码时候 总结，因为时间比较急，改代码也是急了些，并且用了
android WIN DEATH
爱自在的专栏
10-29 9760
http://blog.sina.com.cn/s/blog_46846ade0101cixq.html
Android 闪退分析：WIN DEATH（情况之一）
weixin_33726943的博客
03-29 2289
2019独角兽企业重金招聘Python工程师标准>>> ...
JNI调试
EvoShark的专栏
07-03 923
在Android下使用JNI调用自己实现的so共享库，通过网络链接访问无服务，程序刚启动时就崩溃了，没有任何的提示信息，adb logcat查看运行日志信息： 05-20 21:14:10.288  1382  1520 I ActivityManager: Process com.galen.snappy (pid 6476) has died. 05-20 21:14:10.288  13
出土：跟踪Android应用中的进程死亡
02-04
在Android开发中，进程死亡是开发者常常需要面对的问题，它可能导致应用出现不稳定、用户体验下降甚至数据丢失。"出土：跟踪Android应用中的进程死亡"这个主题深入探讨了如何识别和处理Android应用中的进程被系统杀...
win10蓝屏 - Microsoft Community.rar
10-17
在Windows 10操作系统中，"蓝屏"（也称为蓝屏死机，BSOD：Blue Screen of Death）是用户可能会遇到的一种严重错误情况。它通常伴随着计算机的突然关闭，并显示一个蓝色背景的错误信息屏幕，包含一些技术性的错误代码...
win10蓝屏检查与修复软件
09-23
在IT领域，Windows 10操作系统中的“蓝屏”（Blue Screen of Death，简称BSoD）是一个常见的问题，它通常表示系统遇到了严重错误而无法正常运行。"win10蓝屏检查与修复软件"是专门针对这类问题设计的工具，帮助用户...
win10更新后每天首次开机都出现蓝屏 - Microsoft Community.rar
10-17
蓝屏，全称为“蓝屏死机”（Blue Screen of Death，简称BSoD），是Windows系统遇到严重错误时的一种异常中断显示，通常会显示错误代码和一些调试信息。 在描述中，"win10更新后每天首次开机都出现蓝屏 - Microsoft ...
android native层service代码示例
06-22
在Android系统中，本地服务（Native Service）是运行在C/C++层的服务，它通过Binder机制与Java层的应用组件进行通信。本示例提供了一个完整的Android本地服务实现，包括服务死亡通知、客户端死亡通知以及服务端对...
WindowManager 窗口流程分析
Deaht_Huimie的博客
07-04 746
WindowManager 是窗口，它是一个虚拟的概念，它并不是实际存在的，而是依托于 View ，它的实现类 WindowManagerImpl 更像是个代理人一样，管理着view，我们在 Activity 中可以通过 layout 来添加布局，同样，也可以通过 WindowManager 来实现，如下 class TestActivity extends Activity { p...
操作 sd卡 error
08-26 3344
1.当操作SD卡文件时，弹出SD卡，进程会直接被直接 kill 掉, mbackup不会得到任何提示。 E ProcessKiller: Process com.android.backup (20605) has open file /storage/4A08-16F4/backup/Data/20170817145102/Contact/contact.vcfW InputDispatch
清除APP 数据的时候出现Crash的情况分析
Leif_dong的专栏
05-26 2887
在清除Chromium 浏览器数据的时候出现了异常情况 Crash 复制步骤: info>Storage&cache>CLEAR STORAGE>CLEAR ALL DATA>OK Crash 关键log如下: 5-25 01:15:31.954 1497 3925 I WindowManager: WIN DEATH: Window{7b7e795 u0 org.chromium.chrome/org.chromium.chrome.browser.site...
android 让应用恢复前台显示_android – 当应用程序返回前台时出现问题
weixin_39928993的博客
12-19 240
我的应用程序在与其他应用程序玩一段时间后回到前台时崩溃,我无法找到如何解决它.我的应用程序有一个启动画面活动,它从Web服务加载一些数据并将其放入在扩展应用程序的类中声明的全局静态变量,如this SO question中所述.一旦加载了所有数据,此活动将启动一个Home活动,其中包含一些菜单在应用程序中导航.全球变量用于大多数活动.在某些时候,在玩其他应用程序时,似乎我的应用程序被杀了,因为我可...
Delphi学习案例.docx
最新发布
07-16
Delphi 是一个基于 Object Pascal 的高级编程语言和集成开发环境 (IDE)，适用于 Windows、macOS、iOS 和 Android 平台的快速应用程序开发 (RAD)。以下是一个简单的 Delphi 学习案例，展示如何使用 Delphi 开发一个基本的 Windows 应用程序，该应用程序将实现一个简单的记事本功能。
windowmanager: focus moving from window{51a39a3 u0 d0 com.sensetime.health.m
12-03
WindowManager是安卓系统中的一个关键组件，负责管理窗口的创建、显示和操作。focus moving是指焦点在不同窗口之间的切换。 在这个问题中，window{51a39a3 u0 d0 com.sensetime.health.m}表示一个窗口的唯一标识符。 当焦点从一个窗口移动到另一个窗口时，WindowManager会执行以下步骤： 1. 检测当前窗口是否带有焦点，如果是，则将焦点从当前窗口移除。 2. 检测待切换的目标窗口是否可见，如果不可见，则将其调至可见状态。 3. 将焦点添加到目标窗口上。 在这个问题中，目标窗口的标识符为"window{51a39a3 u0 d0 com.sensetime.health.m}"。 它的含义是：窗口所在进程的用户id为0，设备id为0，包名为com.sensetime.health.m。 这个标识符可以帮助WindowManager唯一地标识出目标窗口，并且根据这个标识符来执行焦点切换的操作。 总之，WindowManager是负责窗口管理的组件，焦点切换是其中的一个重要功能，通过窗口的唯一标识符来进行切换，以实现在不同窗口之间的操作。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值