We are experiencing flaky tests since upgrade from Chrome 61 and ChromeDriver 2.33. Chrome auto upgrade updated Chrome to 64/65 which forced us to upgrade ChromeDriver to 2.36. I reported already intermittent failures on ChromeDriver, but there is some race condition in Chrome itself as many tests ara failing without any change in our code. It is quite random, basically any method can be executed but expected result like click, switch into frame simply does not happen. We wait for elements, so there is no problem with waiting on our side. I suspect the feature "Multi-client remote debugging support" has something to do with this. as problems started in our CI where we experimentally upgraded Chrome to 63.