Does this occur in Chrome 58 (Goto Help>About Google Chrome to update).

This sounds like a duplicate of  issue 704410 

The version in which it happens is the 58.0.3029.81. From what I read, it does not seem to be the same bug, because this only happens when a site is refreshed and simultaneously the mouse wheel is used. It only happens in that moment.

Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Is there a specific page this occurs on? I cannot reproduce it on a Google search results page.

Its happends for example in http:\\www.ole.com.ar\ and this site that I'm developing: http://spi.scmp.com.ar 

Regards!!

Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The one site requires login so can't test there.

But with the other site I can't repro it.

Do you have any experimental features enabled in chrome? I cannot reproduce this on Windows 10 Chrome 58.0.3029.81.  Is this a touchpad or a physical wheel mouse (both appear as a wheel mouse).

I also cannot repro. franciscojad@, do you mean that scrolling stops working even after the page has loaded? Is there any way to make it work again? e.g. refresh? resize window? etc?

+1 confirmation

I've gotten this  bug 20 + times in the last week. I wasn't sure what was causing it until I saw this thread.

I'm able to reproduce this 100% of the time by rapidly scrolling the mouse wheel up and down after hitting Control-R. After doing this, the mouse's scroll wheel will no longer work on that tab. Other tabs (including new tabs) are unaffected.

I just updated to version 58 and that fixed it.

franciscojad@ - Could you please check the issue in latest stable #58.0.3029.96 and please let us know if the issue still persist or not.

Thanks...!!

Closing this for now as there is no repro for the issue. Feel free to open a new issue with the instructions on how to reproduce it if you still see the issue.