[FATAL:input_event_stream_validator.cc(32)] Check failed: ValidateImpl(event, &error_msg_). Pressed touch point (id=1) already exists in previous event (ids=0,1). |
||||
Issue description
Chrome Version: 58.0.3001.0
OS: Android
Not sure if these steps will reproduce the problem.
What steps will reproduce the problem?
(1) Turn talk-back on
(2) Visit https://dump-truck.appspot.com
(3) Was randomly tapping and double tapping to get the "Start" button in one of the sub-pages to open when it crashed.
02-24 16:31:22.989 F/chromium(29222): [FATAL:input_event_stream_validator.cc(32)] Check failed: ValidateImpl(event, &error_msg_). Pressed touch point (id=1) already exists in previous event (ids=0,1).
02-24 16:31:22.989 F/chromium(29222):
02-24 16:31:22.989 F/chromium(29222): Invalid Event: TouchStart (Time: 276715.655000, Modifiers: 0)
02-24 16:31:22.989 F/chromium(29222): {
02-24 16:31:22.989 F/chromium(29222): Touches: 2, DispatchType: 0, CausesScrolling: 0, uniqueTouchEventId: 110
02-24 16:31:22.989 F/chromium(29222): [
02-24 16:31:22.989 F/chromium(29222): (ID: 0, State: 4, ScreenPos: (85.000000, 301.000000), Pos: (85.000000, 220.000000), Radius: (25.843117, 25.843117), Rot: 0.000000, Force: 0.662500, Tilt: (0, 0)),
02-24 16:31:22.989 F/chromium(29222): (ID: 1, State: 2, ScreenPos: (37.000000, 372.000000), Pos: (37.000000, 291.000000), Radius: (25.843117, 25.843117), Rot: 0.000000, Force: 0.650000, Tilt: (0, 0)),
02-24 16:31:22.989 F/chromium(29222): ]
02-24 16:31:22.989 F/chromium(29222): }
02-24 16:31:22.989 F/chromium(29222): #00 0xa1697713 /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so+0x0008a713
02-24 16:31:22.989 F/chromium(29222): #01 0xa16ab757 /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so+0x0009e757
02-24 16:31:22.989 F/chromium(29222): #02 0x97e7d22f /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so+0x0058e22f
02-24 16:31:22.989 F/chromium(29222): #03 0x981f82d1 /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so+0x009092d1
02-24 16:31:22.989 F/chromium(29222): #04 0x9824c1c1 /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so+0x0095d1c1
02-24 16:31:22.989 F/chromium(29222): #05 0x98321127 /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so+0x00a32127
02-24 16:31:22.989 F/chromium(29222): #06 0x9830d3cd /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so+0x00a1e3cd
02-24 16:31:22.989 F/chromium(29222): #07 0x9830d4f3 /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so+0x00a1e4f3
02-24 16:31:22.989 F/chromium(29222): #08 0xa2e7160b /data/dalvik-cache/arm/data@app@org.chromium.chrome-1@base.apk@classes.dex+0x0146260b
02-24 16:31:22.989 F/chromium(29222):
02-24 16:31:22.989 F/libc (29222): Fatal signal 6 (SIGABRT), code -6 in tid 29222 (chromium.chrome)
02-24 16:31:23.093 I/DEBUG ( 188): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-24 16:31:23.093 I/DEBUG ( 188): Build fingerprint: 'google/hammerhead/hammerhead:5.1.1/LMY49S/3276206:userdebug/dev-keys'
02-24 16:31:23.093 I/DEBUG ( 188): Revision: '11'
02-24 16:31:23.093 I/DEBUG ( 188): ABI: 'arm'
02-24 16:31:23.093 I/DEBUG ( 188): pid: 29222, tid: 29222, name: chromium.chrome >>> org.chromium.chrome <<<
02-24 16:31:23.094 I/DEBUG ( 188): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
02-24 16:31:23.121 I/DEBUG ( 188): Abort message: '[FATAL:input_event_stream_validator.cc(32)] Check failed: ValidateImpl(event, &error_msg_). Pressed touch point (id=1) already exists in previous event (ids=0,1).
02-24 16:31:23.121 I/DEBUG ( 188):
02-24 16:31:23.121 I/DEBUG ( 188): Invalid Event: TouchStart (Time: 276715.655000, Modifiers: 0)
02-24 16:31:23.121 I/DEBUG ( 188): {
02-24 16:31:23.121 I/DEBUG ( 188): Touches: 2, DispatchType: 0, CausesScrolling: 0, uniqueTouchEventId: 110
02-24 16:31:23.121 I/DEBUG ( 188): [
02-24 16:31:23.121 I/DEBUG ( 188): (ID: 0, State: 4, ScreenPos: (85.000000, 301.000000), Pos: (85.000000, 220.000000), Radius: (25.843117, 25.843117), Rot: 0.000000, Force: 0.662500, Tilt: (0, 0)),
02-24 16:31:23.121 I/DEBUG ( 188): (ID: 1, State: 2, Screen
02-24 16:31:23.121 I/DEBUG ( 188): r0 00000000 r1 00007226 r2 00000006 r3 00000000
02-24 16:31:23.121 I/DEBUG ( 188): r4 b6f79e38 r5 00000006 r6 0000000b r7 0000010c
02-24 16:31:23.121 I/DEBUG ( 188): r8 beca6b78 r9 00000000 sl b6e4c4b4 fp beca6fc4
02-24 16:31:23.121 I/DEBUG ( 188): ip 00007226 sp beca6a00 lr b6df73c5 pc b6e1a870 cpsr 600f0010
02-24 16:31:23.122 I/DEBUG ( 188):
02-24 16:31:23.122 I/DEBUG ( 188): backtrace:
02-24 16:31:23.122 I/DEBUG ( 188): #00 pc 0003a870 /system/lib/libc.so (tgkill+12)
02-24 16:31:23.122 I/DEBUG ( 188): #01 pc 000173c1 /system/lib/libc.so (pthread_kill+52)
02-24 16:31:23.122 I/DEBUG ( 188): #02 pc 00017fd3 /system/lib/libc.so (raise+10)
02-24 16:31:23.122 I/DEBUG ( 188): #03 pc 00014795 /system/lib/libc.so (__libc_android_abort+36)
02-24 16:31:23.122 I/DEBUG ( 188): #04 pc 00012f44 /system/lib/libc.so (abort+4)
02-24 16:31:23.122 I/DEBUG ( 188): #05 pc 0008a6d3 /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so (_ZN4base5debug13BreakDebuggerEv+18)
02-24 16:31:23.122 I/DEBUG ( 188): #06 pc 0009e8c5 /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so (_ZN7logging10LogMessageD1Ev+600)
02-24 16:31:23.122 I/DEBUG ( 188): #07 pc 0058e22d /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so
02-24 16:31:23.122 I/DEBUG ( 188): #08 pc 009092cf /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so (_ZN7content15InputRouterImpl14SendTouchEventERKNS_20EventWithLatencyInfoIN5blink13WebTouchEventEEE+12)
02-24 16:31:23.122 I/DEBUG ( 188): #09 pc 0095d1c1 /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so (_ZN7content20RenderWidgetHostImpl32ForwardTouchEventWithLatencyInfoERKN5blink13WebTouchEventERKN2ui11LatencyInfoE+256)
02-24 16:31:23.122 I/DEBUG ( 188): #10 pc 00a32127 /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so (_ZN7content27RenderWidgetHostViewAndroid12OnTouchEventERKN2ui11MotionEventE+162)
02-24 16:31:23.122 I/DEBUG ( 188): #11 pc 00a1e3cb /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so
,
Feb 27 2017
In case it helps, happened again with following stack:
02-27 10:56:57.773 F/chromium(28591): [FATAL:input_event_stream_validator.cc(32)] Check failed: ValidateImpl(event, &error_msg_). Pressed touch point (id=1) already exists in previous event (ids=0,1).
02-27 10:56:57.773 F/chromium(28591):
02-27 10:56:57.773 F/chromium(28591): Invalid Event: TouchStart (Time: 515850.442000, Modifiers: 0)
02-27 10:56:57.773 F/chromium(28591): {
02-27 10:56:57.773 F/chromium(28591): Touches: 2, DispatchType: 0, CausesScrolling: 0, uniqueTouchEventId: 52
02-27 10:56:57.773 F/chromium(28591): [
02-27 10:56:57.773 F/chromium(28591): (ID: 0, State: 4, ScreenPos: (153.000000, 167.000000), Pos: (153.000000, 86.000000), Radius: (20.503651, 20.503651), Rot: 0.000000, Force: 0.612500, Tilt: (0, 0)),
02-27 10:56:57.773 F/chromium(28591): (ID: 1, State: 2, ScreenPos: (73.666672, 203.333344), Pos: (73.666672, 122.333336), Radius: (20.503651, 20.503651), Rot: 0.000000, Force: 0.612500, Tilt: (0, 0)),
02-27 10:56:57.773 F/chromium(28591): ]
02-27 10:56:57.773 F/chromium(28591): }
02-27 10:56:57.773 F/chromium(28591): #00 0xa1899713 /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so+0x0008a713
02-27 10:56:57.773 F/chromium(28591): #01 0xa18ad757 /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so+0x0009e757
02-27 10:56:57.773 F/chromium(28591): #02 0x9804122f /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so+0x0058e22f
02-27 10:56:57.773 F/chromium(28591): #03 0x983bc2d1 /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so+0x009092d1
02-27 10:56:57.773 F/chromium(28591): #04 0x984101c1 /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so+0x0095d1c1
02-27 10:56:57.773 F/chromium(28591): #05 0x984e52af /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so+0x00a322af
02-27 10:56:57.773 F/chromium(28591): #06 0x984d1555 /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so+0x00a1e555
02-27 10:56:57.773 F/chromium(28591): #07 0x984d167b /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so+0x00a1e67b
02-27 10:56:57.773 F/chromium(28591): #08 0xa2e7160b /data/dalvik-cache/arm/data@app@org.chromium.chrome-1@base.apk@classes.dex+0x0146260b
02-27 10:56:57.773 F/chromium(28591):
02-27 10:56:57.773 F/libc (28591): Fatal signal 6 (SIGABRT), code -6 in tid 28591 (chromium.chrome)
02-27 10:56:57.830 I/DEBUG ( 188): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-27 10:56:57.830 I/DEBUG ( 188): Build fingerprint: 'google/hammerhead/hammerhead:5.1.1/LMY49S/3276206:userdebug/dev-keys'
02-27 10:56:57.830 I/DEBUG ( 188): Revision: '11'
02-27 10:56:57.830 I/DEBUG ( 188): ABI: 'arm'
02-27 10:56:57.831 I/DEBUG ( 188): pid: 28591, tid: 28591, name: chromium.chrome >>> org.chromium.chrome <<<
02-27 10:56:57.831 I/DEBUG ( 188): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
02-27 10:56:57.862 I/DEBUG ( 188): Abort message: '[FATAL:input_event_stream_validator.cc(32)] Check failed: ValidateImpl(event, &error_msg_). Pressed touch point (id=1) already exists in previous event (ids=0,1).
02-27 10:56:57.862 I/DEBUG ( 188):
02-27 10:56:57.862 I/DEBUG ( 188): Invalid Event: TouchStart (Time: 515850.442000, Modifiers: 0)
02-27 10:56:57.862 I/DEBUG ( 188): {
02-27 10:56:57.862 I/DEBUG ( 188): Touches: 2, DispatchType: 0, CausesScrolling: 0, uniqueTouchEventId: 52
02-27 10:56:57.862 I/DEBUG ( 188): [
02-27 10:56:57.862 I/DEBUG ( 188): (ID: 0, State: 4, ScreenPos: (153.000000, 167.000000), Pos: (153.000000, 86.000000), Radius: (20.503651, 20.503651), Rot: 0.000000, Force: 0.612500, Tilt: (0, 0)),
02-27 10:56:57.862 I/DEBUG ( 188): (ID: 1, State: 2, Screen
02-27 10:56:57.862 I/DEBUG ( 188): r0 00000000 r1 00006faf r2 00000006 r3 00000000
02-27 10:56:57.862 I/DEBUG ( 188): r4 b6f79e38 r5 00000006 r6 0000000b r7 0000010c
02-27 10:56:57.863 I/DEBUG ( 188): r8 beca6bf8 r9 00000000 sl b6e4c4b4 fp beca7044
02-27 10:56:57.863 I/DEBUG ( 188): ip 00006faf sp beca6a80 lr b6df73c5 pc b6e1a870 cpsr 600f0010
02-27 10:56:57.863 I/DEBUG ( 188):
02-27 10:56:57.863 I/DEBUG ( 188): backtrace:
02-27 10:56:57.864 I/DEBUG ( 188): #00 pc 0003a870 /system/lib/libc.so (tgkill+12)
02-27 10:56:57.864 I/DEBUG ( 188): #01 pc 000173c1 /system/lib/libc.so (pthread_kill+52)
02-27 10:56:57.864 I/DEBUG ( 188): #02 pc 00017fd3 /system/lib/libc.so (raise+10)
02-27 10:56:57.864 I/DEBUG ( 188): #03 pc 00014795 /system/lib/libc.so (__libc_android_abort+36)
02-27 10:56:57.864 I/DEBUG ( 188): #04 pc 00012f44 /system/lib/libc.so (abort+4)
02-27 10:56:57.864 I/DEBUG ( 188): #05 pc 0008a6d3 /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so (_ZN4base5debug13BreakDebuggerEv+18)
02-27 10:56:57.864 I/DEBUG ( 188): #06 pc 0009e8c5 /data/app/org.chromium.chrome-1/lib/arm/libbase.cr.so (_ZN7logging10LogMessageD1Ev+600)
02-27 10:56:57.864 I/DEBUG ( 188): #07 pc 0058e22d /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so
02-27 10:56:57.864 I/DEBUG ( 188): #08 pc 009092cf /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so (_ZN7content15InputRouterImpl14SendTouchEventERKNS_20EventWithLatencyInfoIN5blink13WebTouchEventEEE+12)
02-27 10:56:57.864 I/DEBUG ( 188): #09 pc 0095d1c1 /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so (_ZN7content20RenderWidgetHostImpl32ForwardTouchEventWithLatencyInfoERKN5blink13WebTouchEventERKN2ui11LatencyInfoE+256)
02-27 10:56:57.864 I/DEBUG ( 188): #10 pc 00a322af /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so (_ZN7content27RenderWidgetHostViewAndroid12OnTouchEventERKN2ui11MotionEventE+162)
02-27 10:56:57.864 I/DEBUG ( 188): #11 pc 00a1e553 /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so
02-27 10:56:57.864 I/DEBUG ( 188): #12 pc 00a1e679 /data/app/org.chromium.chrome-1/lib/arm/libcontent.cr.so (Java_org_chromium_content_browser_ContentViewCore_nativeOnTouchEvent+272)
02-27 10:56:57.864 I/DEBUG ( 188): #13 pc 0048260b /data/dalvik-cache/arm/data@app@org.chromium.chrome-1@base.apk@classes.dex
,
Feb 27 2017
This is probably related: https://bugs.chromium.org/p/chromium/issues/detail?id=696369
,
Mar 2 2017
I think this might be caused by my pass through touch event queue. The pre filter signal goes out before the acks. So it could tell the stream validator something non-sensible.
,
Mar 2 2017
No this can't be my pass through touch event queue because this predates those changes. csahsi@ what hardware is this on? (is it chrome on android on chromeos perhaps?)
,
Mar 2 2017
Hi - This was on Android. It happens quite often on Android.
,
Jul 26 2017
,
Jan 10
|
||||
►
Sign in to add a comment |
||||
Comment 1 Deleted