//进程是30970 //特殊情况下,如果PID是0,说明发生ANR之前,这个进程被LowMemoryKiller杀死了或者出现了Crash。这种情况下,是无法接收到系统的广播或者按键消息的,故而出现ANR //ANR具体发生的包名 08-01 19:17:05.155 1000 1304 1328 I am_anr : [0,30970,com.android.systemui,551042573,Input dispatching timed out (StatusBar, Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 54. Wait queue head age: 9044.8ms.)] //ANR具体发生的包名 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: ANR in com.android.systemui //ANR发生的原因是Input dispatching timed out 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: PID: 30970 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: Reason: Input dispatching timed out (StatusBar, Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 54. Wait queue head age: 9044.8ms.) //三个数字分别是1分钟、5分钟、15分钟内系统的平均负荷 //当CPU完全空闲的时候,平均负荷为0;当CPU工作量饱和的时候,平均负荷为1,通过Load可以判断系统负荷是否过重 //大致可以这样区分: //当系统负荷持续大于0.7,你必须开始调查了,问题出在哪里,防止情况恶化。 //当系统负荷持续大于1.0,你必须动手寻找解决办法,把这个值降下来。 //当系统负荷达到5.0,就表明你的系统有很严重的问题 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: Load: 46.53 / 37.82 / 34.77 //ANR发生的时候,Top进程的Cpu占用情况,user代表是用户空间,kernel是内核空间 //查看每个CPU的使用频度:adb shell cat /sys/devices/system/cpu/cpu1/cpufreq/stats/time_in_state //一般如下规律: //1. kswapd0 cpu占用率偏高,系统整体运行会缓慢,从而引起各种ANR。把问题转给"内存优化",请他们进行优化 //2. logd CPU占用率偏高,也会引起系统卡顿和ANR,因为各个进程输出LOG的操作被阻塞从而执行的极为缓慢 //3. Vold占用CPU过高,会引起系统卡顿和ANR,请负责存储的同学先调查 //4. qcom.sensor CPU占用率过高,会引起卡顿,请系统同学调查 //5. 应用自身CPU占用率较高,高概率应用自身问题 //6. 应用处于D状态,发生ANR,如果最后的操作是refriger,那么是应用被冻结了,正常情况下是功耗优化引起的。 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: CPU usage from 0ms to 23321ms later (2020-08-01 19:17:04.850 to 2020-08-01 19:17:28.171) with 99% awake: 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: 36% 30970/com.android.systemui: 25% user + 10% kernel / faults: 11945 minor 24 major 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: 35% 20903/com.tencent.mobileqq:video: 28% user + 6.4% kernel / faults: 6413 minor 23 major 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: 28% 555/surfaceflinger: 16% user + 12% kernel / faults: 1846 minor 2 major 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: 26% 498/android.hardware.audio@5.0-service-***: 21% user + 4.9% kernel / faults: 13 minor 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: 18% 1304/system_server: 9.5% user + 8.7% kernel / faults: 9666 minor 329 major 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: 17% 3919/com.***.service: 10% user + 6.7% kernel / faults: 8604 minor 30 major 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: 16% 28827/com.tencent.qqmusic: 9.2% user + 7.3% kernel / faults: 9299 minor 18 major 08-01 19:17:28.258 1000 1304 1328 E ActivityManager: 16% 142/kswapd0: 0% user + 16% kernel ...