[FATAL:input_handler_proxy.cc(857)] Check failed: expect_scroll_update_end_ |
|||
Issue descriptionChrome Version : trunk/master OS Version: Android LMY48I, Nexus 5 URLs (if applicable) : chrome://media-internals What steps will reproduce the problem? 1. Not sure, I play a video in one tab to test and then switch to chrome://media-internals tab using the tab switcher. What is the expected result? Chrome doesn't crash. What happens instead of that? Chrome's renderer crashes (sad tab) Happened to me yesterday and now today. The stack trace is attached.
,
Mar 9 2017
This should be caused by the incorrect order of gesture fling events. I'm working on the fix.
,
Mar 14 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ad977926ecd213a1063fb7d429d6fd1d5ee7dce7 commit ad977926ecd213a1063fb7d429d6fd1d5ee7dce7 Author: chongz <chongz@chromium.org> Date: Tue Mar 14 18:45:37 2017 [Compositor event queue] Queue GestureFlingStart/Cancel together with scroll/pinch Currently only |GestureScroll*| and |GesturePinch*| will be put into the queue. We should cover |GestureFlingStart/Cancel| as well since it's order-sensitive. BUG= 693289 Review-Url: https://codereview.chromium.org/2746513002 Cr-Commit-Position: refs/heads/master@{#456772} [modify] https://crrev.com/ad977926ecd213a1063fb7d429d6fd1d5ee7dce7/ui/events/blink/blink_event_util.cc [modify] https://crrev.com/ad977926ecd213a1063fb7d429d6fd1d5ee7dce7/ui/events/blink/blink_event_util.h [modify] https://crrev.com/ad977926ecd213a1063fb7d429d6fd1d5ee7dce7/ui/events/blink/input_handler_proxy.cc [modify] https://crrev.com/ad977926ecd213a1063fb7d429d6fd1d5ee7dce7/ui/events/blink/input_handler_proxy_unittest.cc
,
Mar 14 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bokan@chromium.org
, Feb 23 2017Labels: Hotlist-Input-Dev
Status: Assigned (was: Untriaged)