我有一个RK3288盒子,正在开发一款应用程序。
我遇到的问题一直困扰着我。我无法调试任何内容。
每次我连接调试器并在主线程上设置断点后,我的应用程序在几秒钟后崩溃。 下面是当这种情况发生时的日志记录:
现在,我做了一些研究,发现在正常情况下ANR是指当超过5秒没有响应触摸事件时触发,这似乎就是这里发生的事情。
虽然这对于应用程序的正常操作来说没问题,但如果我在一个按钮的OnClickListener上放置一个断点,这种情况就不应该发生,但在我的情况下确实发生了。
这在任何其他手机上都没有发生过,只在这个板子上发生。
我该怎么修复这个问题并最终进行调试呢?
需要提到的是,我还有操作系统代码(AOSP + kernel),我已经自己编译/安装了它,所以如果需要的话,我可以修改操作系统。
如果有用的话,以下是ANR跟踪信息: https://pastebin.com/C3dh9rzK 编辑:
似乎这不是应用的问题,而是操作系统的问题。 我能够在一个全新的项目中重现崩溃,在这个项目中,我只添加了一个按钮和一个OnClickListener。然后我在监听器内部放置了一个断点,连接了调试器并点击了按钮。KA-BOOOM。
我遇到的问题一直困扰着我。我无法调试任何内容。
每次我连接调试器并在主线程上设置断点后,我的应用程序在几秒钟后崩溃。 下面是当这种情况发生时的日志记录:
05-02 20:52:39.734 459-534/system_process I/InputDispatcher: Application is not responding: Window{3026b626 u0 com.kushtrim.playground/com.kushtrim.playground.MainActivity}. It has been 5001.8ms since event, 5001.6ms since wait started. Reason: 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: 17. Wait queue head age: 5505.1ms.
05-02 20:52:39.794 459-534/system_process I/WindowManagerService: Input event dispatching timed out sending to com.kushtrim.playground/com.kushtrim.playground.MainActivity. Reason: 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: 17. Wait queue head age: 5505.1ms.
05-02 20:52:39.811 459-482/system_process I/Process: Sending signal. PID: 8790 SIG: 3
05-02 20:52:39.812 8790-8799/com.kushtrim.playground I/art: Thread[5,tid=8799,WaitingInMainSignalCatcherLoop,Thread*=0xb7294b58,peer=0x12c000a0,"Signal Catcher"]: reacting to signal 3
05-02 20:52:39.970 459-482/system_process I/Process: Sending signal. PID: 459 SIG: 3
05-02 20:52:39.970 459-468/system_process I/art: Thread[5,tid=468,WaitingInMainSignalCatcherLoop,Thread*=0xb7113410,peer=0x12c020a0,"Signal Catcher"]: reacting to signal 3
05-02 20:52:39.970 8790-8799/com.kushtrim.playground I/art: Wrote stack traces to '/data/anr/traces.txt'
05-02 20:52:40.123 459-478/system_process E/SensorsHal: poll() failed (Interrupted system call)
05-02 20:52:40.824 459-981/system_process E/WifiHAL: Error polling socket
05-02 20:52:40.900 6611-6661/com.solaborate.hello D/Webrtc_calls: SocketIoStatus conected: true , socketId: 9U55YZnsB0EeSDcHACui
05-02 20:52:41.018 459-482/system_process I/Process: Sending signal. PID: 852 SIG: 3
05-02 20:52:41.019 852-864/com.android.phone I/art: Thread[5,tid=864,WaitingInMainSignalCatcherLoop,Thread*=0xb7113410,peer=0x12c000a0,"Signal Catcher"]: reacting to signal 3
05-02 20:52:41.023 459-1442/system_process W/ActivityManagerService: Missing app error report, app = com.kushtrim.playground crashing = false notResponding = true
05-02 20:52:41.028 459-468/system_process I/art: Wrote stack traces to '/data/anr/traces.txt'
05-02 20:52:41.028 459-482/system_process I/Process: Sending signal. PID: 811 SIG: 3
05-02 20:52:41.029 811-820/com.android.inputmethod.latin I/art: Thread[5,tid=820,WaitingInMainSignalCatcherLoop,Thread*=0xb7112928,peer=0x12c000a0,"Signal Catcher"]: reacting to signal 3
05-02 20:52:41.152 811-820/com.android.inputmethod.latin I/art: Wrote stack traces to '/data/anr/traces.txt'
05-02 20:52:41.152 459-482/system_process I/Process: Sending signal. PID: 628 SIG: 3
05-02 20:52:41.152 628-636/com.android.systemui I/art: Thread[5,tid=636,WaitingInMainSignalCatcherLoop,Thread*=0xb7112928,peer=0x12c000a0,"Signal Catcher"]: reacting to signal 3
05-02 20:52:41.209 852-864/com.android.phone I/art: Wrote stack traces to '/data/anr/traces.txt'
05-02 20:52:41.209 459-482/system_process I/Process: Sending signal. PID: 712 SIG: 3
05-02 20:52:41.209 712-719/com.cghs.stresstest I/art: Thread[5,tid=719,WaitingInMainSignalCatcherLoop,Thread*=0xb7112a18,peer=0x12c000a0,"Signal Catcher"]: reacting to signal 3
05-02 20:52:41.286 712-719/com.cghs.stresstest I/art: Wrote stack traces to '/data/anr/traces.txt'
05-02 20:52:41.286 459-482/system_process I/Process: Sending signal. PID: 591 SIG: 3
05-02 20:52:41.286 591-600/android.process.media I/art: Thread[5,tid=600,WaitingInMainSignalCatcherLoop,Thread*=0xb7112928,peer=0x12c000a0,"Signal Catcher"]: reacting to signal 3
05-02 20:52:41.313 628-636/com.android.systemui I/art: Wrote stack traces to '/data/anr/traces.txt'
05-02 20:52:41.396 591-600/android.process.media I/art: Wrote stack traces to '/data/anr/traces.txt'
05-02 20:52:41.554 459-913/system_process W/ActivityManagerService: Missing app error report, app = com.kushtrim.playground crashing = false notResponding = true
05-02 20:52:42.094 459-944/system_process W/ActivityManagerService: Missing app error report, app = com.kushtrim.playground crashing = false notResponding = true
05-02 20:52:43.304 459-1982/system_process W/ActivityManagerService: Missing app error report, app = com.kushtrim.playground crashing = false notResponding = true
05-02 20:52:43.869 459-482/system_process I/art: Explicit concurrent mark sweep GC freed 58037(3MB) AllocSpace objects, 10(257KB) LOS objects, 33% free, 19MB/28MB, paused 811us total 53.345ms
05-02 20:52:43.883 459-482/system_process W/ProcessCpuTracker: Skipping unknown process pid 9185
05-02 20:52:44.189 459-4388/system_process W/ActivityManagerService: Missing app error report, app = com.kushtrim.playground crashing = false notResponding = true
05-02 20:52:44.418 459-482/system_process I/Process: Sending signal. PID: 1155 SIG: 3
05-02 20:52:44.418 1155-1164/com.waxrain.airplaydmr I/art: Thread[5,tid=1164,WaitingInMainSignalCatcherLoop,Thread*=0xb7112928,peer=0x32c070a0,"Signal Catcher"]: reacting to signal 3
05-02 20:52:44.540 1155-1164/com.waxrain.airplaydmr I/art: Wrote stack traces to '/data/anr/traces.txt'
05-02 20:52:44.549 459-482/system_process E/ActivityManagerService: ANR in com.kushtrim.playground (com.kushtrim.playground/.MainActivity)
PID: 8790
Reason: Input dispatching timed out (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: 17. Wait queue head age: 5505.1ms.)
Load: 1.48 / 1.36 / 1.86
CPU usage from 567ms to -4733ms ago:
31% 459/system_server: 14% user + 17% kernel / faults: 6486 minor 5 major
0% 164/debuggerd: 0% user + 0% kernel / faults: 3474 minor 5 major
8.6% 161/surfaceflinger: 5.6% user + 3% kernel / faults: 629 minor
0% 852/com.android.phone: 0% user + 0% kernel / faults: 2463 minor
2.8% 8790/com.kushtrim.playground: 1.1% user + 1.7% kernel / faults: 1497 minor
0.6% 628/com.android.systemui: 0.3% user + 0.2% kernel / faults: 1800 minor 2 major
0% 811/com.android.inputmethod.latin: 0% user + 0% kernel / faults: 2089 minor
2.2% 1155/com.waxrain.airplaydmr: 1.5% user + 0.7% kernel / faults: 1754 minor
2% 174/adbd: 0.1% user + 1.8% kernel / faults: 564 minor
0% 591/android.process.media: 0% user + 0% kernel / faults: 2149 minor 1 major
0% 712/com.cghs.stresstest: 0% user + 0% kernel / faults: 1984 minor
0.9% 69/cfinteractive: 0% user + 0.9% kernel
0.5% 153/dhd_dpc: 0% user + 0.5% kernel
0.5% 155/logd: 0.3% user + 0.1% kernel
0.3% 68/rk-fb: 0% user + 0.3% kernel
0.3% 152/dhd_watchdog_th: 0% user + 0.3% kernel
0.1% 8/rcu_preempt: 0% user + 0.1% kernel
0.1% 14/ksoftirqd/1: 0% user + 0.1% kernel
0.1% 19/ksoftirqd/2: 0% user + 0.1% kernel
0.1% 24/ksoftirqd/3: 0% user + 0.1% kernel
0.1% 67/fb-vsync: 0% user + 0.1% kernel
0.1% 110/mmcqd/0: 0% user + 0.1% kernel
0.1% 122/irq/198-mma8452: 0% user + 0.1% kernel
0.1% 507/mediaserver: 0% user + 0.1% kernel / faults: 12 minor
0% 1174/com.android.settings: 0% user + 0% kernel / faults: 22 minor
0.1% 1252/wdog2: 0% user + 0.1% kernel
0.1% 1486/com.skype.raider: 0.1% user + 0% kernel / faults: 6 minor
0.1% 2355/com.tencent.mm:push: 0% user + 0.1% kernel / faults: 331 minor
0.1% 4835/wpa_supplicant: 0% user + 0.1% kernel
0.1% 6611/com.solaborate.hello: 0.1% user + 0% kernel / faults: 12 minor
0% 7891/kworker/2:2: 0% user + 0% kernel
0.1% 7974/kworker/0:1: 0% user + 0.1% kernel
0.1% 8875/logcat: 0.1% user + 0% kernel
+0% 9168/kworker/u8:4: 0% user + 0% kernel
19% TOTAL: 8.1% user + 11% kernel + 0.3% iowait + 0% softirq
CPU usage from 4062ms to 4577ms later:
7.6% 459/system_server: 3.8% user + 3.8% kernel / faults: 27 minor
3.8% 482/ActivityManager: 1.9% user + 1.9% kernel
1.9% 487/android.display: 1.9% user + 0% kernel
5.7% 161/surfaceflinger: 1.9% user + 3.8% kernel / faults: 14 minor
1.9% 161/surfaceflinger: 1.9% user + 0% kernel
1.9% 314/DispSync: 0% user + 1.9% kernel
1.9% 433/surfaceflinger: 0% user + 1.9% kernel
1.9% 552/Binder_4: 1.9% user + 0% kernel
1.3% 14/ksoftirqd/1: 0% user + 1.3% kernel
1.3% 19/ksoftirqd/2: 0% user + 1.3% kernel
1.4% 153/dhd_dpc: 0% user + 1.4% kernel
1.4% 174/adbd: 0% user + 1.4% kernel / faults: 60 minor
1.4% 174/adbd: 1.4% user + 0% kernel
1.5% 1155/com.waxrain.airplaydmr: 1.5% user + 0% kernel
6.4% TOTAL: 2.4% user + 3.9% kernel
现在,我做了一些研究,发现在正常情况下ANR是指当超过5秒没有响应触摸事件时触发,这似乎就是这里发生的事情。
虽然这对于应用程序的正常操作来说没问题,但如果我在一个按钮的OnClickListener上放置一个断点,这种情况就不应该发生,但在我的情况下确实发生了。
这在任何其他手机上都没有发生过,只在这个板子上发生。
我该怎么修复这个问题并最终进行调试呢?
需要提到的是,我还有操作系统代码(AOSP + kernel),我已经自己编译/安装了它,所以如果需要的话,我可以修改操作系统。
如果有用的话,以下是ANR跟踪信息: https://pastebin.com/C3dh9rzK 编辑:
似乎这不是应用的问题,而是操作系统的问题。 我能够在一个全新的项目中重现崩溃,在这个项目中,我只添加了一个按钮和一个OnClickListener。然后我在监听器内部放置了一个断点,连接了调试器并点击了按钮。KA-BOOOM。
android.os.Debug.waitForDebugger()
并在此之后插入断点吗? - Haris Qurashiadb shell am set-debug-app --persistent
方法解决了这个问题。 - Attila Tanyi