Waiting because the touched window has not finished

最新推荐文章于 2024-06-11 09:43:37 发布
原创 最新推荐文章于 2024-06-11 09:43:37 发布 · 3.9k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#Android view #Android ontouch

本文针对应用程序中出现的等待输入现象进行了分析，并给出了具体的优化建议。指出在onTouchEvent中应避免进行耗时操作，在Move中避免频繁创建新对象，以减少虚拟机垃圾回收的压力。

Waiting for application to become ready for input: xxxx Reason: Waiting because the touched window has not finished processing the input events that were previously delivered to it.

  1. 在onTouchEvevent里避免做耗时操作。
  2. 在Move里避免生成对象，过多的new新对象会导致虚拟机来不及释放。(Wait for concurrent GC blocked)

问题提供者：H!ccup


ANR问题：Reason: Input dispatching timed out (Waiting to send key event because the focused window ...
I_always_believe的博客
12-26 820
首先去Android 右侧 device exploer点开，data之下---anr---可以找到有效信息，根据有效信息，可以判断代码具体哪个地方报错。该类问题一般都是主线程阻塞，尽量不要再主线程操作耗时操作。我当时也是借鉴了该博主的方法，成功找到报错地方....首先这个是ANR，在代码中写的异常捕捉捕捉不到；
Android开发之ANR原因分析
xiayiye5的博客
06-17 984
第一步拿到anr日志文件 bogon:wyze-doorbell-wireless-android-14 xiayiye5$ adb shell 进入手机目录 HS8917QC:/ $ cd data/anr 进入anr目录 HS8917QC:/data/anr $ ls 查看anr日志劣币哦啊文件 traces.txt traces.txt.bugreport HS8917QC:/data/anr $ ls -l 查看anr最近的一次列表文件 total 6408 -rw-rw-rw- 1 syst
记一次解决ANR问题
本然233的博客
10-23 1304
一次测试过程中出现anr ANR Input dispatching timed out（Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered it over 500.0ms ago. 1）导出tr...
Input dispatching timed out (Waiting to send non-key event because the touched window has not finish
chezabo6116的博客
06-11 2633
系统设定了一个阈值（500.0ms），如果在此期间窗口（如Activity）没有完成处理之前的输入事件，就会触发这个警告。Wait queue head age: 6420.5ms: 队列中最旧的事件等待处理的时间已经超过了6秒，这表明系统在处理输入事件方面存在严重延迟。UI线程被阻塞：可能是因为在主线程（UI线程）上执行了耗时的操作，如网络请求、大量计算或数据库操作。优化UI：减少不必要的布局嵌套，避免复杂的绘制操作，使用高效的动画实现。检查第三方库：确保使用的库是最新版本，并且没有已知的性能问题。
Reason: Input dispatching timed out (Waiting to send non-key event because the touched window
chezabo6116的博客
03-22 3848
这个错误信息表示你的应用出现了ANR（Application Not Responding），原因是输入分发超时。系统在尝试发送一个非键盘事件（如触摸事件）时，目标窗口未能在规定时间（通常是500ms）内完成对一些之前传递给它的输入事件的处理。这通常意味着主线程（UI线程）被阻塞了太长时间，没有及时处理输入事件或完成其他任务。
AnrManager: startAsyncDump: AnrDumpRecord{ 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: 6. Wait queue head age: 5511.6ms.) ProcessRecord{e154cc2 2374:com.waterflowing.light/u0a13} IsCompleted:false IsCancelled:false } 09-30 00:51:44.816 486 501 I AnrManager: appNotResponding-got this lock: ProcessRecord{e154cc2 2374:com.waterflowing.light/u0a13} 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: 6. Wait queue head age: 5511.6ms.) 09-30 00:51:44.816 486 501 I AnrManager: dumpAnrDebugInfo begin: AnrDumpRecord{ 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: 6. Wait queue head age: 5511.6ms.) ProcessRecord{e154cc2 2374:com.waterflowing.light/u0a13} IsCompleted:false IsCancelled:false }, isAsyncDump = false 09-30 00:51:44.817 486 501 I AnrManager: dumpAnrDebugInfoLocked: AnrDumpRecord{ 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: 6. Wait queue head age: 5511.6ms.) ProcessRecord{e154cc2 2374:com.waterflowing.light/u0a13} IsCompleted:false IsCancelled:false }, isAsyncDump = false 09-30 00:51:44.843 486 2867 I AnrManager: sys/kernel/debug/binder/timeout_log isn't exist 09-30 00:51:44.857 486 501 I AnrManager: dumpStackTraces begin! 分析日志
最新发布
09-30
### **日志分析：ANR（Application Not Responding）问题** 这个日志显示 **`com.waterflowing.light`（PID: 2374, UID: u0a13）** 发生了 **输入事件超时（Input dispatching timed out）**，触发了 **ANR（应用无...
代码解释：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: 2. Wait queue head age: 6051.6ms.)
06-04
这个错误通常在 Android 应用程序中出现，意味着应用程序正在等待某个操作完成，但是这个操作花费的时间太长了，超过了系统设置的等待时间。具体来说，这个错误通常是由于 UI 线程被阻塞或者处理一个耗时的操作导致...
ANR in com.waterflowing.light (com.waterflowing.light/com.waterflowing.pad.MainActivity), time=170356504 行 3130: 09-28 09:09:56.688 480 495 I AnrManager: 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: 25. Wait queue head age: 16813.9ms.) 行 3131: 09-28 09:09:56.688 480 495 I AnrManager: 分析日志
09-29
这个ANR日志表明应用`com.waterflowing.light`的主界面`MainActivity`在处理输入事件时发生了响应超时（ANR）。具体分析如下： 1. **关键信息**： ... - 界面：`MainActivity` - 类型：`Input dispatching timed out`...
2025-08-28 17:27:05.786 30980-30980 FileUtils pid-30980 W deleteRecursive：删除成功: /storage/emulated/0/Android/data/com.kotei.overseas.navi/files/overseas/data/mapoffline/v1/1MCztmBt85mbwQr8hRKtgg/ocm-map/ARCHIVES 2025-08-28 17:27:05.787 30980-30980 FileUtils pid-30980 W deleteRecursive：删除成功: /storage/emulated/0/Android/data/com.kotei.overseas.navi/files/overseas/data/mapoffline/v1/1MCztmBt85mbwQr8hRKtgg/ocm-map/ARCHIVES/07 2025-08-28 17:27:05.794 30980-30980 chatty pid-30980 I uid=1000(system) com.kotei.overseas.navi identical 57 lines 2025-08-28 17:27:05.794 30980-30980 FileUtils pid-30980 W deleteRecursive：删除成功: /storage/emulated/0/Android/data/com.kotei.overseas.navi/files/overseas/data/mapoffline/v1/1MCztmBt85mbwQr8hRKtgg/ocm-map/ARCHIVES/07 2025-08-28 17:27:05.794 30980-30980 FileUtils pid-30980 W deleteRecursive：删除成功: /storage/emulated/0/Android/data/com.kotei.overseas.navi/files/overseas/data/mapoffline/v1/1MCztmBt85mbwQr8hRKtgg/ocm-map/ARCHIVES/07 2025-08-28 17:27:05.799 30980-30980 chatty pid-30980 I uid=1000(system) com.kotei.overseas.navi identical 42 lines 2025-08-28 17:27:05.799 30980-30980 FileUtils pid-30980 W deleteRecursive：删除成功: /storage/emulated/0/Android/data/com.kotei.overseas.navi/files/overseas/data/mapoffline/v1/1MCztmBt85mbwQr8hRKtgg/ocm-map/ARCHIVES/07 2025-08-28 17:27:05.799 30980-30980 FileUtils pid-30980 W deleteRecursive：删除成功: /storage/emulated/0/Android/data/com.kotei.overseas.navi/files/overseas/data/mapoffline/v1/1MCztmBt85mbwQr8hRKtgg/ocm-map/ARCHIVES 2025-08-28 17:27:05.800 30980-30980 FileUtils pid-30980 W deleteRecursive：删除成功: /storage/emulated/0/Android/data/com.kotei.overseas.navi/files/overseas/data/mapoffline/v1/1MCztmBt85mbwQr8hRKtgg/ocm-map/ARCHIVES/4c 2025-08-28 17:27:05.806 30980-30980 chatty pid-30980 I uid=1000(system) com.kotei.overseas.navi identical 48 lines 2025-08-28 17:27:05.806 30980-30980 FileUtils pid-30980 W deleteRecursive：删除成功: /storage/emulated/0/Android/data/com.kotei.overseas.navi/files/overseas/data/mapoffline/v1/1MCztmBt85mbwQr8hRKtgg/ocm-map/ARCHIVES/4c 2025-08-28 17:27:07.104 1081-1797 InputDispatcher system_server I ====>>dispatch targets=(5863fe8 com.kotei.overseas.navi/com.kotei.overseas.navi.base.MainActivity (server);edge-swipe (server);poweroff (server);PointerEventDispatcher0 (server);) 2025-08-28 17:27:07.114 2051-2051 DF_SystemUI com.android.systemui I [log_sysui][DFEdgeBackGestureManager] onMotionEvent currentActivityName==com.kotei.overseas.navi.base.MainActivity mIsBackGestureAllowed==true isBackViewVisibility=false mAllowGesture = false 2025-08-28 17:27:12.881 1081-1797 InputDispatcher system_server I Application is not responding: Window{5863fe8 u0 com.kotei.overseas.navi/com.kotei.overseas.navi.base.MainActivity}. It has been 5002.9ms since event, 5001.4ms 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: 2. Wait queue head age: 5777.1ms. 2025-08-28 17:27:12.887 1081-1797 WindowManager system_server I Input event dispatching timed out sending to com.kotei.overseas.navi/com.kotei.overseas.navi.base.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: 2. Wait queue head age: 5777.1ms. 2025-08-28 17:27:29.066 1081-1797 ActivityManager system_server E ANR in com.kotei.overseas.navi (com.kotei.overseas.navi/.base.MainActivity) PID: 30980 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: 2. Wait queue head age: 5777.1ms.) Parent: com.kotei.overseas.navi/.base.MainActivity Load: 5.92 / 5.45 / 4.7 CPU usage from 0ms to 16008ms later (2025-08-28 17:27:13.005 to 2025-08-28 17:27:29.012): 48% 30980/com.kotei.overseas.navi: 12% user + 35% kernel / faults: 18219 minor 67 major 8.7% 993/android.hardware.avm@1.0-service: 0% user + 8.6% kernel 8.6% 1081/system_server: 4.5% user + 4.1% kernel / faults: 8889 minor 71 major 7.9% 2635/com.iflytek.cutefly.speechclient.hmi: 3.3% user + 4.5% kernel / faults: 9668 minor 75 major 0.1% 440/vold: 0% user + 0.1% kernel / faults: 644 minor 57 major 0% 1076/media.codec: 0% user + 0% kernel / faults: 30291 minor 118 major 5.6% 780/surfaceflinger: 2.3% user + 3.3% kernel / faults: 548 minor 5 major 3.6% 2821/com.dftc.systemsettings: 1.9% user + 1.6% kernel / faults: 4439 minor 13 major 3.4% 3166/com.isa.navi: 1.9% user + 1.4% kernel / faults: 3715 minor 274 major 3.1% 30949/kworker/u16:12: 0% user + 3.1% kernel 2.6% 430/logd: 0.7% user + 1.8% kernel / faults: 5 minor 2.4% 28574/kworker/u16:8: 0% user + 2.4% kernel 2.1% 87/kswapd0: 0% user + 2.1% kernel 2.1% 30583/kworker/u16:0: 0% user + 2.1% kernel 2% 1926/com.android.bluetooth: 1.1% user + 0.9% kernel / faults: 6247 minor 30 major 1.9% 647/android.hardware.audio@2.0-service: 0% user + 1.9% kernel 1.8% 2485/kworker/u16:4: 0% user + 1.8% kernel 1.6% 766/audioserver: 0.2% user + 1.3% kernel / faults: 151 minor 1.6% 2051/com.android.systemui: 1% user + 0.5% kernel / faults: 6091 minor 55 major 1.5% 18127/kworker/u16:1: 0% user + 1.5% kernel 0% 1106/media.swcodec: 0% user + 0% kernel / faults: 10597 minor 16 major 1.4% 660/android.hardware.graphics.composer@2.3-service: 0.5% user + 0.8% kernel / faults: 404 minor 18 major 1.3% 833/logcat: 0.5% user + 0.7% kernel / faults: 6 minor 0% 3035/com.android.inputmethod.latin: 0% user + 0% kernel / faults: 4841 minor 15 major 0.8% 665/android.hardware.sensors@1.0-service: 0.4% user + 0.3% kernel / faults: 102 minor 1 major 0.8% 3196/sh: 0% user + 0.8% kernel / faults: 2030 minor 0.7% 3688/com.dftc.bluetoothpolicy: 0.4% user + 0.2% kernel / faults: 3333 minor 33 major 0.6% 2483/com.android.phone: 0.4% user + 0.2% kernel / faults: 3215 minor 32 major 0.6% 652/android.hardware.automotive.dfvehicle@1.0-service: 0.1% user + 0.4% kernel / faults: 1 minor 0.6% 2177/com.df.tbox.service: 0.4% user + 0.1% kernel / faults: 3741 minor 16 major 0.5% 2528/com.df.signal: 0.3% user + 0.2% kernel / faults: 3491 minor 17 major 0.4% 2203/com.dftc.car: 0.2% user + 0.2% kernel / faults: 3129 minor 19 major 0.4% 3694/irq/68-1b8e200.: 0% user + 0.4% kernel 0.4% 252/crtc_commit:88: 0% user + 0.4% kernel 0.4% 550/netd: 0.1% user + 0.3% kernel / faults: 596 minor 2 major 0.4% 977/sh: 0% user + 0.4% kernel / faults: 915 minor 0% 2150/com.df.systempolicy: 0% user + 0% kernel / faults: 3551 minor 20 major 0% 2285/com.dftc.carinput: 0% user + 0% kernel / faults: 3559 minor 16 major 0.4% 2391/com.df.tsp.service: 0.3% user + 0% kernel / faults: 3187 minor 7 major 0.4% 2429/com.dftc.power: 0.1% user + 0.3% kernel / faults: 3298 minor 7 major 0% 3495/com.dftc.hvac: 0% user + 0% kernel / faults: 3559 minor 54 major 0% 3522/com.dftc.DFRadioService: 0% user + 0% kernel / faults: 3559 minor 48 major 0% 3556/com.dftc.DFAudioService: 0% user + 0% kernel / faults: 3751 minor 66 major 0% 1050/media.extractor: 0% user + 0% kernel / faults: 2754 minor 6 major 0% 2252/com.df.time: 0% user + 0% kernel / faults: 3483 minor 23 major 0% 2357/com.qualcomm.qti.telephonyservice: 0% user + 0% kernel / faults: 3496 minor 19 major 0% 3424/com.raite.bgappmgr: 0% user + 0% kernel / faults: 3985 minor 37 major
08-29
从日志分析来看，这是一个典型的Android应用ANR（Application Not Responding）问题，发生在`com.kotei.overseas.navi`导航应用的主活动中。以下是关键分析： **ANR直接原因**： 1. 输入事件超时（5002.9ms未响应）...
InputContextCallback.waitForResultLocked导致的ANR
AAAndroid的博客
03-08 378
InputContextCallback.waitForResultLocked 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. waitqueue length = 35, head.seq =
Input dispatching timed out ANR问题分析
Aile
05-15 1万+
导言: 项目中碰到ANR很正常,要是碰到了,也很开心,表明你的代码还不够优秀,仍需继续努力,而这片日记只是工作中碰到的一个,在这里只是解决ANR的思路,不做什么什么的分析原理,工作中更多的是发现问题和快速解决问题,而不是什么原理,这个只能当做是知识的深入,但是要适可而止,是不是! ANR日志 这是使用bugly拦截的ANR事件,有时候会更显眼,更容易找到问题之所在 Input dispatching timed out ANR Input dispatching timed out (Waiting to
ANR-Input dispatching timed out
倒骑驴走着瞧的博客
05-28 5349
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: 6. Wait queue head age: 8813.6ms.) 出现该问题的情
Android ANR 问题第二弹------Input超时实战问题解析上
热门推荐
为码消得人憔悴
05-30 8万+
在前面的Android ANR 问题第二弹一文中，我们简诉了Android Input超时的原因，我们了解到系统Input系统分发Input的事件时如果有5s超时会触发应用ANR。在实际开发测试中，我们也会经常遇到Input超时导致的ANR问题，那么现在我们就以实际问题分析一下Input超时的ANR问题，描述一下实际开发测试中我们应该如何定位问题的原因。本文基于AndroidO(8.1)系统。实战...
记一次解决ANR问题的笔记
小马快跑的博客
05-03 8692
记录一次解决ANR问题的笔记： 起因： 在项目提测之后，QA同学提了一个ANR的bug，然后按照她的步骤走了一遍，发现没有复现，所以怀疑是机型或者是账号的问题，于是把QA同学的手机借来又试了一遍，还是没有复现，于是怀疑跟账号有关系（APP需要登录），于是把她的账号也要过来又走了一遍，果然多次来回点击，若干次重复操作后就ANR了，既然出现了ANR，就来排查trace文件吧 排查： 1...
ANR Input dispatching timed out
记录生活中的点滴美好，活在当下！
03-25 5178
Reason: Input dispatching timed out (Waiting to send key event because the focused window has not finished processing all of the input events that were previously delivered to it. Outbound queue le...
ANR问题浅析
chewbee的专栏
05-23 1万+
我们在Android应用开发中，会经常遇到ANR问题。本文将从ANR产生的原因、ANR的分类、ANR问题的分析、ANR问题的常见解决办法这几个方面来介绍ANR。最后会通过分析ANR源码，了解ANR产生的过程。 一、ANR简介 ANR是Application Not Responding的简称，即应用无响应。 ANR产生的原因是由于应用在主线程阻塞了，导致界面无响应。超时的原因一般为两种：
ANR分析-WaitingPerformingGc
zwq1457的专栏
11-03 2889
10-12 17:32:02.726 1120 1159 I am_anr : [0,17331,com.flipkart.android,955792964,Input dispatching timed out (Waiting to send key event because the focused window has not finished processing all of the
应用NE导致进程变为T状态出现了ANR
一杯咖啡的专栏
08-16 998
Activity: com.android.chrome/org.chromium.chrome.browser.ChromeTabbedActivity Subject: Input dispatching timed out (Waiting to send key event because the focused window has not finished processing ...
android anr 产生的类型及原因
binbinbintony的博客
02-26 1947
android anr 产生的条件 android 系统中anr的本质是主线程无法响应。而导致主线程无法响应的原因大致如下： 主线程请求网络资源，数据库访问或者io访问...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值