New issue
Advanced search Search tips

Issue 756437 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Wheel scrolling occasionally stops working

Project Member Reported by bokan@chromium.org, Aug 17 2017

Issue description

Chrome Version       : 62.0.3178.0
OS Version: Linux

What steps will reproduce the problem?
0. Enable wheel latching and async wheel events (I suspect these are related)
1. Scroll with wheel on page/subscroller

What is the expected result?
Page should scroll

What happens instead of that?
Nothing happens.

This happens quite occasionally so it's difficult to reproduce. When it does happen, wheels seem to be ignored. I can still scroll using the scrollbars and drag-and-drop autoscroll but that doesn't fix wheels - we're somehow getting into a bad state. 

Wheel scrolling still works in other tabs.

I've attached a trace I took once I got into this state. The affected renderer is pid 9691 (Code Search - synced_property). For e.g. see the InputHandlerManager::HandleInputEvent call in the compositor thread @ 1,282.914ms. We're receiving the GSB and GSU in the input handler proxy but there isn't much information after that. It looks like those get ACKd to the browser with "No Consumer Exists"



 

Comment 1 by bokan@chromium.org, Aug 17 2017

Owner: sahel@chromium.org
Status: Assigned (was: Untriaged)
Trace attached.

Sahel, could you ptal and see if you can tell what the issue is? Since it's so hard to repro I suspect you'll need to determine what state is affecting this and add some release asserts to catch when that state goes bad.
trace_noscroll.json.gz
2.1 MB Download

Comment 2 by bokan@chromium.org, Aug 17 2017

One additinal data point: a reload solves the issue.

Comment 3 by bokan@chromium.org, Sep 7 2017

Still hitting this in 62.0.3202.9
Labels: -Pri-2 Pri-3
Sahel@ any update on this. You have been working on bunch of similar cases in the past quarters. Just wondering whether this was resolved as a result or not.

Sign in to add a comment