Thanks for filing the issue!

Unable to reproduce the issue on reported chrome version 71.0.3578.80 using Windows 10 Surface Pro with the below mentioned steps.
1. Launched Chrome
2. Navigated to a random web page.
3. Clicked the web links present in the page.
4. Tried two finger scrolling (up/down) and Side ways(left/right)
We were able to scroll up/down and pages we navigated back & forth respectively without any issues.  

@Reporter: Could you please let us know if we have missed anything in the process. Please check the same in a new profile without any apps & extensions and let us know if we have missed anything in the process. Any further inputs from your end may be helpful.  

Today I installed Chrome Canary version 73.0.3642.0
With just a few tabs open I am still experiencing the two finger scrolling freeze
It only seems to happen in Chrome
I have zero extensions enabled
Fresh install of Canary
This has been on-going since August. Been on various builds of Windows including 1709, 1803, and presently 1809.
Happy to provide any relevant logs

Thank you for providing more feedback. Adding the requester to the cc list.

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

Re-tested the issue on reported chrome version 71.0.3578.80 & on latest canary  73.0.3642.0 using Windows 10 Pro 1803 with the steps mentioned in comment#2, still we couldn't reproduce the issue from our end. Hence removing Needs-Bisect label and requesting someone from "Blink>Scroll" team to help in further triaging it.

Thanks!

Chao, do you have any suggestion how to proceed with this issue? Any trick that we might be missing here in case it is related to precision touch pad?

I did not seeing any other similar reports now. Record a tracing would help us see the issue.

https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs

More specific reproduce steps and specific model would also help us reproduce.

Also AV software maybe relevant, let me know it can reproduce without AV software.

If user keep getting trouble with this because AV software. We may need a flag for user disabling DMaip.

Just have a offline chat with dtapuska@, what he saw in  Issue 647038  was AV software injected a window on the top of Chrome in Chrome's window tree that break Dmaip's events handling.

1. If you have spy++ you can use it to check the windows tree of Chrome.
2. Try add flag --disable-features=PrecisionTouchpad to shortcut and see it can still reproduce.

Correct Windows tree would be:

Chrome_WidgetWin
 + Chrome Legacy Window [1 or n]
 + D3D window

Reporter could you provide the information requested? 

Yes it is still happening with AV (Symantec Endpoint Protection Enterprise 14.5) disabled. I will try to do a trace. How can I securely provide that data?

*Symantec 14.2

Thank you for providing more feedback. Adding the requester to the cc list.

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

I dont see an option for "PrecisionTouchpad" under chrome://flags

How can I access this setting to try disabling it?

Thanks

1. add flag --disable-features=PrecisionTouchpad can disable it.
2. you can send the tracing to my email.

Thanks but I still dont understand where to type "add flag --disable-features=PrecisionTouchpad"

I do not see "PrecisionTouchpad" under chrome://flags. I am assuming the command you are recommending that I run adds it as an option there so I can toggle on and off?

Thanks

Also interesting is looking back at the stable release history, it looks like PrecisionTouchpad support was added in mid-August and that is exactly when this issue started for me...

In the target field

Deleted: Screen Shot 2019-01-01 at 11.24.32.png 358 KB

	Screen Shot 2019-01-01 at 11.24.32.png 358 KB View Download

Ok got it added there now. Is there a way to test whether it took?

You can see pinch zoom is gone if it applied.

Thanks, I was able to verify it is now disabled and so far zero issues. I would've likely seen a freeze by now but will keep monitoring and report back if I do encounter. Since this seems to confirm there is indeed a PrecisionTouchpad issue, any idea how it can be fixed or is the fix just to keep it disabled? If so, perhaps a flag should be added in the Chrome settings to allow users to more easily disable it? Please let me know if any further information is needed from me. Thanks!

I can not fix it without any reproduce steps or tracing information. We may remove the flag anytime since it is pretty stable. You are only one user reporting this issue, I also checked reddit. Please send me your tracing when scrolling freeze.

Ok I will revert bag and do a tracing. There are reports I saw on Microsoft's forum, Google products forum, and reddit, I counted at least two dozen people across these websites reporting the same issue. It is indeed weird it is not more widely reported...

Yes, I have seen reports before we land PrecisionTouchpad and before https://bugs.chromium.org/p/chromium/issues/detail?id=847611 fixed. You are the only one after that.

BTW, I still not confirm this issue.

I went to do the tracing as it was happening and I don't know which tracing settings I should select?

Web developer
Input latency
Rendering
Javascript and rendering
Frame Viewer
Manually select settings

.....and which categories?

Another interesting tidbit is when I had precisiontouch disabled, Chrome seemed to be much snappier this past week... I also have not run into black screens that I am experiencing in the other issue 914911. Finally, another interesting tidbit is I use Firefox as a backup browser, launching it rarely, maybe 1-2x per day for a quick session... every time I launched firefox while chrome is open, my cursor was nowhere to be found and firefox keeps freezing... when I had precision touchpad disabled this past week, my cursor appeared in firefox and it was not freezing up. Possible its just coincidence but very very interesting... something seems to be going on...

Input latency or just select all. It is weird on Firefox stuff. For precision touchpad what we do is registering chrome window can receive Direct Manipulation events. I also test it on Surface Go but can not reproduce.

As I posted in my other bug report, interestingly enough, Chrome seems much more stable all of the sudden. I will continue using but I was generally getting the touch pad freezing 1-2+ dozen times per day. It has not happened in almost an entire week. I have been updating Chrome Canary daily. Was there a code change? I also happen to run a Windows update (latest monthly cumulative for Win 10 1809) last week around the same time so unclear if that may have played a role. Either way this is the smoothest its been and longest without issues since mid-to-late August!

So I had a couple two finger scrolling freezes yesterday and one just now. So its not completely gone but seems to be less frequent... Problem is every time it happens and I go to start a tracing it is resolved by the time I return to the tab and scroll... I dont know how I am going to capture a tracing...

I do not think we have any related code update for this after 72.0.3595.0. If switch tab can recover the issue. It seems like Direct Manipulation stucks at a wrong state eg. state change without viewport stop calls.

https://cs.chromium.org/chromium/src/ui/base/win/direct_manipulation.cc?rcl=b1936659c7f820bba9dd0fa5dcbea22ef4daa961&l=145

But I don't know what is incorrect here.

I dont know if switching tabs fixes it or if it just unfreezes in the amount of time that it was taking me to start tracing and return to the tab. Some times the freezes last 5-10 seconds some times 30 seconds some times a minute.

So the two finger scrolling freezes are happening more often again. Six times in past day. Every time I switch tabs and back to the one where two finger scrolling froze, its unfrozen. So it may indeed be direct manipulation getting stuck as you have suggested...