Figure

请帮忙分析下这个问题

11月8号release版本复现此问题
Tlog&ANR目录见附件

Hi 赵飞
附件里的ANR日志，无法打开，无法解压缩
请帮忙重新上传一份，感谢

Log已上传至FTP
ftp://cdiot@192.168.87.46/Pre_figure/Test_Log/Bug_113494/Tlog&ANR.zip

■ Current conclusion
看起来有点像是SystemUI Crash了,导致Hwui绘制异常了

■ My analysis
从trace信息看,nSyncAndDrawFrame出现了异常
"main" prio=5 tid=1 Native | group="main" sCount=1 ucsCount=0 flags=1 obj=0x717513a8 self=0xb400007c91f25be0 | sysTid=2036 nice=0 cgrp=default sched=0/0 handle=0x7e5b2e04f8 | state=S schedstat=( 1247173349143 1232846138935 2383247 ) utm=76502 stm=48214 core=4 HZ=100 | stack=0x7fe06b7000-0x7fe06b9000 stackSize=8188KB | held mutexes=
native: #00 pc 000000000004def0 /apex/com.android.runtime/lib64/bionic/libc.so (syscall+32)
native: #01 pc 00000000000527bc /apex/com.android.runtime/lib64/bionic/libc.so (__futex_wait_ex(void volatile*, bool, int, bool, timespec const*)+148)
native: #02 pc 00000000000b5c50 /apex/com.android.runtime/lib64/bionic/libc.so (pthread_cond_wait+84)
native: #03 pc 000000000036bff0 /system/lib64/libhwui.so (android::uirenderer::renderthread::DrawFrameTask::postAndWait()+256)
native: #04 pc 000000000036bebc /system/lib64/libhwui.so (android::uirenderer::renderthread::RenderProxy::syncAndDrawFrame()+52)
at android.graphics.HardwareRenderer.nSyncAndDrawFrame(Native method)
at android.graphics.HardwareRenderer.syncAndDrawFrame(HardwareRenderer.java:456)

出现异常的原因有可能是SystemUI Crash,导致NavigationBar绘制出错引起的

11-08 06:39:54.396 1139 1710 I WindowManager: ANR in NavigationBar0. Reason:b784fa8 NavigationBar0 (server) is not responding. Waited 5001ms for MotionEvent(deviceId=-1, eventTime=17456610000000, source=0x00001002, displayId=0, action=DOWN, actionButton=0x00000000, flags=0x00000000, metaState=0x00000000, buttonState=0x00000000, classification=NONE, edgeFlags=0x00000000, xPrecision=1.0, yPrecision=1.0, xCursorPosition=nan, yCursorPosition=nan, pointers=[0: (122.0, 706.0)]), policyFlags=0x6b000000

SystemUI Crash在另外一个票上已经解决了
https://dev.thundercomm.com/gerrit/c/general/platform/frameworks/base/+/161275

// CRASH: com.android.systemui:screenshot (pid 12924)
// Short Msg: java.lang.IllegalStateException
// Long Msg: java.lang.IllegalStateException: Image is already closed
// Build Label: TC/figure_CN/figure:12/SKQ1.220201.001/1319:userdebug/test-keys
// Build Changelist: 1319
// Build Time: 1667843376000
// java.lang.IllegalStateException: Image is already closed
// at android.media.Image.throwISEIfImageIsInvalid(Image.java:73)
// at android.media.ImageReader$SurfaceImage.getHardwareBuffer(ImageReader.java:989)
// at com.android.systemui.screenshot.ImageTile.<init>(ImageTile.java:57)
// at com.android.systemui.screenshot.ScrollCaptureController.onCaptureResult(ScrollCaptureController.java:263)
// at com.android.systemui.screenshot.ScrollCaptureController.lambda$requestNextTile$2(ScrollCaptureController.java:201)
// at com.android.systemui.screenshot.ScrollCaptureController.$r8$lambda$4sO_sN6742S0RDVb5SN-JLbf7OE(Unknown Source:0)
// at com.android.systemui.screenshot.ScrollCaptureController$$ExternalSyntheticLambda2.run(Unknown Source:2)
// at android.os.Handler.handleCallback(Handler.java:938)
// at android.os.Handler.dispatchMessage(Handler.java:99)
// at android.os.Looper.loopOnce(Looper.java:201)
// at android.os.Looper.loop(Looper.java:288)
// at android.app.ActivityThread.main(ActivityThread.java:7880)
// at java.lang.reflect.Method.invoke(Native Method)
// at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
// at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1009)

■ Next Action
请在下个版本在验证一下 是否有相同的anr或者crash信息

11月11号DB复现此问题1次

错误信息：

// NOT RESPONDING: com.android.systemui (pid 2004)
ANR in com.android.systemui
PID: 2004
Reason: Input dispatching timed out (a65ede4 NotificationShade (server) is not responding. Waited 5001ms for KeyEvent(deviceId=-1, eventTime=22903022000000, source=0x00000101, displayId=-1, action=DOWN, flags=0x00000008, keyCode=82, scanCode=0, metaState=0x00000000, repeatCount=0), policyFlags=0x6b000000)
ErrorId: 0ebf202f-ecc2-42dc-af68-df5270158d6e
Frozen: false
Load: 5.62 / 5.64 / 5.99
----- Output from /proc/pressure/memory -----
some avg10=0.00 avg60=0.00 avg300=0.00 total=3469361
full avg10=0.00 avg60=0.00 avg300=0.00 total=1676046
----- End output from /proc/pressure/memory -----

CPU usage from 0ms to 17265ms later (2022-11-11 11:08:12.924 to 2022-11-11 11:08:30.190):
  92% 1232/tlog: 2.8% user + 89% kernel / faults: 4 minor
  91% 1058/sensors.qti: 18% user + 73% kernel
  70% 2004/com.android.systemui: 50% user + 20% kernel / faults: 24181 minor
  54% 4797/tlog: 2% user + 52% kernel / faults: 1 minor
  52% 1123/system_server: 17% user + 34% kernel / faults: 61367 minor
  38% 956/vendor.qti.hardware.display.composer-service: 12% user + 25% kernel / faults: 597 minor
  31% 1047/surfaceflinger: 14% user + 17% kernel / faults: 2537 minor
  3.3% 1329/media.codec: 1.2% user + 2.1% kernel / faults: 22526 minor
  7.6% 21256/com.android.settings: 5.1% user + 2.4% kernel / faults: 3298 minor
  6.9% 2941/com.hht.lebocast: 3% user + 3.9% kernel / faults: 1183 minor
  6.2% 1278/installd: 0.4% user + 5.8% kernel / faults: 23 minor
  6.1% 1403/media.swcodec: 1.2% user + 4.8% kernel / faults: 10764 minor
  5.2% 5417/com.sohu.inputmethod.sogou.car: 2.4% user + 2.8% kernel / faults: 2133 minor
  5.1% 3582/com.android.calendar: 2.5% user + 2.5% kernel / faults: 1650 minor
  5% 772/crtc_commit:125: 0% user + 5% kernel
...

日志见FTP：
ftp://cdiot@192.168.87.46/Pre_figure/Test_Log/Bug_113739/Tlog&ANR.zip

11月16号DB版本（user）及11月17号Release版本均未复现此问题
暂时关闭此问题