android播放器加载时候按返回导致ANR异常，求大神

Question

我自己写的一个android播放器，滑动屏幕进行快进，然后视频处于加载的时候，点击返回按钮，就会出现ANR异常。求解，想了好久了，求大神相救。不胜感激

 03-10 13:18:44.878: E/mdb_debug(350): mdb_usb_sharenet.c:send_sharenet_msg[L-232]: mdb usb share net channel is not ready!: 0, Success
03-10 13:18:54.468: E/ActivityManager(960): ANR in com.edufound.dayvideo (com.edufound.dayvideo/.GameCpp)
03-10 13:18:54.468: E/ActivityManager(960): PID: 8639
03-10 13:18:54.468: E/ActivityManager(960): Reason: Input dispatching timed out (Waiting because no window has focus but there is a focused application that may eventually add a window when it finishes starting up.)
03-10 13:18:54.468: E/ActivityManager(960): Load: 18.71 / 18.09 / 17.94
03-10 13:18:54.468: E/ActivityManager(960): CPU usage from 6858ms to 83ms ago:
03-10 13:18:54.468: E/ActivityManager(960):   4.2% 960/system_server: 3.5% user + 0.7% kernel / faults: 384 minor
03-10 13:18:54.468: E/ActivityManager(960):   2.4% 202/surfaceflinger: 1.1% user + 1.3% kernel / faults: 16 minor
03-10 13:18:54.468: E/ActivityManager(960):   2.4% 1299/com.baidu.input_mi: 2.1% user + 0.2% kernel / faults: 2363 minor
03-10 13:18:54.468: E/ActivityManager(960):   1.9% 10951/mediaserver: 0% user + 1.9% kernel
03-10 13:18:54.468: E/ActivityManager(960):   1.6% 1172/com.android.systemui: 1.1% user + 0.4% kernel / faults: 13 minor
03-10 13:18:54.468: E/ActivityManager(960):   1.4% 33/kworker/u:1H: 0% user + 1.4% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.7% 733/RX_Thread: 0% user + 0.7% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.5% 462/charger_monitor: 0% user + 0.5% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.5% 1745/mpdecision: 0% user + 0.5% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.3% 8133/kworker/u:2: 0% user + 0.3% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.4% 130/w1_bus_master1: 0% user + 0.4% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.4% 8142/kworker/u:14: 0% user + 0.4% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.4% 8851/kworker/0:0H: 0% user + 0.4% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.2% 3/ksoftirqd/0: 0% user + 0.2% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.1% 7/kworker/u:0H: 0% user + 0.1% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.2% 418/sensors.qcom: 0.2% user + 0% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.2% 705/mdss_fb0: 0% user + 0.2% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.2% 731/TX_Thread: 0% user + 0.2% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.2% 8134/kworker/u:5: 0% user + 0.2% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.2% 8161/kworker/0:2H: 0% user + 0.2% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.2% 13784/adbd: 0% user + 0.2% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0% 199/netd: 0% user + 0% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0% 211/thermal-engine: 0% user + 0% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0% 312/sdcard: 0% user + 0% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0% 339/irq/289-wcd9xxx: 0% user + 0% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0% 1356/com.android.phone: 0% user + 0% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0% 1378/com.qualcomm.services.location: 0% user + 0% kernel / faults: 1 minor
03-10 13:18:54.468: E/ActivityManager(960):   0% 1562/android.process.acore: 0% user + 0% kernel / faults: 4 minor
03-10 13:18:54.468: E/ActivityManager(960):   0.1% 5372/logcat: 0.1% user + 0% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0% 12099/com.tencent.mm: 0% user + 0% kernel / faults: 12 minor
03-10 13:18:54.468: E/ActivityManager(960):   0.1% 12819/com.miui.weather2:weatherservice: 0% user + 0.1% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0% 15554/com.miui.guardprovider: 0% user + 0% kernel
03-10 13:18:54.468: E/ActivityManager(960):   0.1% 22737/com.tencent.mm:push: 0% user + 0.1% kernel
03-10 13:18:54.468: E/ActivityManager(960): 19% TOTAL: 8.4% user + 10% kernel + 0.6% iowait + 0.3% softirq
03-10 13:18:54.468: E/ActivityManager(960): CPU usage from 2062ms to 2579ms later with 99% awake:
03-10 13:18:54.468: E/ActivityManager(960):   5.6% 960/system_server: 0% user + 5.6% kernel
03-10 13:18:54.468: E/ActivityManager(960):     3.7% 989/ActivityManager: 0% user + 3.7% kernel
03-10 13:18:54.468: E/ActivityManager(960):     1.8% 960/system_server: 0% user + 1.8% kernel
03-10 13:18:54.468: E/ActivityManager(960):     1.8% 1464/Binder_B: 1.8% user + 0% kernel
03-10 13:18:54.468: E/ActivityManager(960):   2.5% 462/charger_monitor: 0% user + 2.5% kernel
03-10 13:18:54.468: E/ActivityManager(960):   1.1% 3/ksoftirqd/0: 0% user + 1.1% kernel
03-10 13:18:54.468: E/ActivityManager(960):   1.3% 1172/com.android.systemui: 1.3% user + 0% kernel
03-10 13:18:54.468: E/ActivityManager(960):   1.4% 1745/mpdecision: 0% user + 1.4% kernel
03-10 13:18:54.468: E/ActivityManager(960):   1.4% 10951/mediaserver: 0% user + 1.4% kernel
03-10 13:18:54.468: E/ActivityManager(960): 8.5% TOTAL: 1.4% user + 7.1% kernel
03-10 13:19:00.268: E/AudioSink(10951): received unknown event type: 1 inside CallbackWrapper !

Answer 1

/data/anr 目录有对应的异常信息和java call stack。 你可以知道当前在做什么，是什么阻止了你的事件处理。

我想你的问题的解决方法最好是将用户操作事件转成队列或者起一个timer 后处理，避免多个事件堵塞，尽量保证只想用用户最后输入的事件。

当然也可能是解码等操作没有返回引起的，那么你需要在单独的线程去执行这些动作，避免堵塞ui进程。