title: Chrome processes are not killed after using quit() method on Chrome 65
body: <p>I've problem after update my Chrome browser to Version 65.0.3325.162 (latest)</p>
  
  <p>When my tests start after done each method in task manager there appear  extra zombie Chrome process which take many resources of CPU.</p>
  
  <p><a href="https://i.stack.imgur.com/mJoc0.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/mJoc0.png" alt="Task manager"></a></p>
  
  <p>IS there any change with method driver.quit() on Chrome 65? I will add that, on previous version of Chrome browser all was OK.</p>
  
  <p>I use data provider so using method quit() is necessary for correctly working on my test suite.</p>
  
  <p>I use mothod terminate() to close browser after each test class.</p>
  
  <p>My stuff:
  Windows 10
  Selenium WebDriver 
  ChromeDriver 2.36
  Selenium WebDriver 2.20</p>
  
  <pre><code>@AfterClass(alwaysRun = true)
      protected void terminate() {
          if (browser != null) {
              try {
                  browser.quit();
                  browser = null;
              } catch (UnreachableBrowserException ex) {
                  TestReporter.log(ex.getMessage());
              } catch (NoSuchSessionException noSuchSessionException) {
                  TestReporter.log("Tried to quit browser with NULL session: " + noSuchSessionException.getMessage());
              }
          }
  
          if (application != null) {
              application = null;
          }
      }
  </code></pre>