UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0

Steps to reproduce the problem:
1. Clone the github repo I set up to reproduce this problem and follow the instructions listed in its readme.md file:

https://github.com/mvanderkamp/devtools_bug

(The source code is actually quite short, but is long enough, and the steps to view the problem detailed enough that I decided a github repo would be a better approach).

What is the expected behavior?
Chrome should only emit one TouchEvent, and break on that TouchEvent if asked to do so.

What went wrong?
Chrome emits two seemingly identical TouchEvents, and skips any and all breakpoints encountered while processing the first TouchEvent.

Did this work before? N/A 

Chrome version: 68.0.3440.106 (Official Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit)  Channel: stable
OS Version: 4.15.0-33-generic #36~16.04.1-Ubuntu
Flash Version: Shockwave Flash 30.0 r0

I don't know if this is related to the chrome version on my tablet or the chromium version on my desktop. In the github repo I list details on both.
 

Deleted: devtools_bug_demo.ogv 4.8 MB

	devtools_bug_demo.ogv 4.8 MB View Download