UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Steps to reproduce the problem:
Bugs like  crbug.com/309093  annoy the serious web developer community for years now and contribute to bad rep.

I request hereby to make more use of "end-user" testing tools like selenium to execute at least parts of the chromium test suite to have a better tool chain quality. Fixing bugs in tools only used by chromium devs doesn't add to the overall quality of the overall result which includes important tools like selenium.

See https://github.com/SeleniumHQ/selenium/issues/2025 for example.

Or at least add some stress tests for the most important end-user dev tools. Here is one for the start: https://github.com/jjYBdx4IL/selenium-start-stop-stresstest

What is the expected behavior?

What went wrong?
as one example, chromium hangs on CI systems. selenium devs not aware of the issues for years now.

Did this work before? N/A 

Chrome version: 51.0.2704.103  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 22.0 r0