TimeoutException causes certain commands to hang forever

[GoogleCodeExporter]

Issue Description:
I want to use Webdriver.set_page_load_timeout() and was testing what would 
happen when it fails. I didn't experience any problems with Firefox or 
PhantomJS, I did get into situations where Chrome would crash (hangs 
indefinitely).

I'm handling the TimeoutException thrown by set_page_load_timeout and trying to 
proceed with a test script (nevermind why :) ). If I call Webdriver.close() or 
Webdriver.execute_script("window.open()") after the exception from the 
page_load_timeout is thrown, the browser crashes. There are no problems before 
the exception is thrown. There are no problems when other types of exceptions 
are thrown, or in other browsers.

Steps to reproduce (if relevant, you MUST provide a simplified html page or
link to public site):
<enter repro steps here>

See above. I could provide a test script if necessary but I think this should 
be fairly easy to reproduce if you walk through a situation like the one 
described above.

I'm using:
Session info: chrome=43.0.2357.134
Driver info: chromedriver=2.13.307647
(5a7d0541ebc58e69994a6fb2ed930f45261f3c29),platform=Windows NT 6.1 SP1 x86_64
Python 3.4.2
Selenium 2.45.0

Note: I tried to follow the "helpful tip" to turn on verbose logging below 
(self.driver = webdriver.Chrome(service_args=["--verbose"])), and that *also* 
seemed to cause Chrome to crash (browser spins up and does nothing).

-----Other helpful tips:
Attach your chromedriver log with verbose logging enabled (see
http://goo.gl/5Sx8mC for how to do this).

Original issue reported on code.google.com by dsh...@indeed.com on 14 Jul 2015 at 9:27

[GoogleCodeExporter]

I should have also said that this doesn't happen when window.get(some_url) or 
other commands I've tried are called after the TimeoutException.

Original comment by dsh...@indeed.com on 14 Jul 2015 at 9:30

[GoogleCodeExporter]

 dshuga@

Thanks for filling bug. can you please provide sample testcase and html to 
reproduce this issue ?

Original comment by agau...@chromium.org on 17 Jul 2015 at 10:32

• Added labels: Needs-Feedback

[GoogleCodeExporter]

Attached a demonstration of the bug. Spin up Firefox instead of Chrome and the 
unit test will pass.

Original comment by dsh...@indeed.com on 17 Jul 2015 at 4:37

Attachments:

• chrome_bug.py

[GoogleCodeExporter]

This issue is reproducible in latest version of ChromeDriver 2.16
Testcase:- attached per comment#3

Original comment by agau...@chromium.org on 20 Jul 2015 at 8:09

• Changed state: Untriaged