title: selenium in python - one timeout causes all subsequent requests to timeout
body: <p>Chrome driver version: 2.41
  Chrome version: 69.0.3497.92</p>
  
  <p>Here's my code sending multiple requests to one webdriver with exception handling:</p>
  
  <pre><code>from selenium import webdriver
  from selenium.common.exceptions import *
  
  options = webdriver.ChromeOptions()
  options.add_argument('--headless')
  options.add_argument('--no-sandbox')
  
  driver = webdriver.Chrome('/usr/local/bin/chromedriver', chrome_options=options)
  driver.set_page_load_timeout(30)
  
  for link in links:
      try:
          driver.get(link)
      except TimeoutException as e:
          # do something
          continue
      except Exception as e:
          # do some other thing
          continue
  </code></pre>
  
  <p>The expected behavior was if a TimeoutException is thrown, I would just continue making requests to the next link and so on. However, what I am getting is that when one TimeoutException occurs, all the rest of the links also throw TimeoutExceptions.</p>
  
  <p>Here's the the relevant log from chrome's logger.</p>
  
  <blockquote>
  <pre><code>[1536872569.507][SEVERE]: Timed out receiving message from renderer: 29.449
  [1536872569.509][INFO]: Timed out. Stopping navigation...
  [1536872569.509][DEBUG]: DEVTOOLS COMMAND Page.stopLoading (id=1243) {
  
  }
  [1536872569.509][DEBUG]: DEVTOOLS RESPONSE Page.stopLoading (id=1243) {
  
  }
  [1536872569.509][DEBUG]: DEVTOOLS COMMAND Runtime.evaluate (id=1244) {
     "expression": "1"
  }
  [1536872569.510][SEVERE]: Timed out receiving message from renderer: -0.002
  [1536872569.513][INFO]: Done waiting for pending navigations. Status: timeout
  [1536872569.513][INFO]: RESPONSE Navigate timeout
    (Session info: headless chrome=69.0.3497.92)
  [1536872569.516][INFO]: COMMAND Navigate {
    "sessionId": "9caf0bad68147065f14c9c22632cd6d8",
     "url": "www.example.com"
  }
  [1536872569.516][DEBUG]: DEVTOOLS EVENT Page.frameStoppedLoading {
     "frameId": "620369B66F0605C0CE359F34F9D95E36"
  }
  [1536872569.516][DEBUG]: DEVTOOLS RESPONSE Runtime.evaluate (id=1244) {
     "result": {
        "description": "1",
        "type": "number",
        "value": 1
     }
  }
  [1536872569.516][INFO]: Waiting for pending navigations...
  [1536872569.516][DEBUG]: DEVTOOLS COMMAND Runtime.evaluate (id=1245) {
     "expression": "1"
  }
  [1536872569.517][DEBUG]: DEVTOOLS RESPONSE Runtime.evaluate (id=1245) {
     "result": {
        "description": "1",
        "type": "number",
        "value": 1
     }
  }
  [1536872599.516][SEVERE]: Timed out receiving message from renderer: 30.000
  [1536872599.518][INFO]: Timed out. Stopping navigation...
  [1536872599.518][DEBUG]: DEVTOOLS COMMAND Page.stopLoading (id=1246) {
  
  }
  [1536872599.518][DEBUG]: DEVTOOLS RESPONSE Page.stopLoading (id=1246) {
  
  }
  [1536872599.518][DEBUG]: DEVTOOLS COMMAND Runtime.evaluate (id=1247) {
     "expression": "1"
  }
  [1536872599.518][SEVERE]: Timed out receiving message from renderer: -0.002
  [1536872599.522][INFO]: Done waiting for pending navigations. Status: timeout
  [1536872599.522][INFO]: RESPONSE Navigate timeout
    (Session info: headless chrome=69.0.3497.92)
  [1536872599.524][INFO]: COMMAND Navigate {
     "sessionId": "9caf0bad68147065f14c9c22632cd6d8",
     "url": "www.example2.com"
  }
  </code></pre>
  </blockquote>
  
  <p>The following are differences I found when comparing this event to other subsequent requests that finished without any exceptions.</p>
  
  <p>1) <code>DEVTOOLS EVENT Page.frameStoppedLoading</code> comes immediately after sending a request to the new 'www.example.com' link.</p>
  
  <p>2) the response to <code>DEVTOOLS COMMAND Runtime.evaluate (id=1244)</code>, which was sent from the previous link, is logged after the request to the new URL.</p>
  
  <p><strong>Question:</strong> is there any other way to handle this other than restarting the driver with each TimeoutException?</p>
  
  <p>If someone could also elaborate on the behavior I'd really appreciate it. Thank you.</p>