Skip to content
This repository has been archived by the owner. It is now read-only.

Error when calling Browser.close using IE 10+ #7092

Closed
lukeis opened this issue Mar 4, 2016 · 5 comments
Closed

Error when calling Browser.close using IE 10+ #7092

lukeis opened this issue Mar 4, 2016 · 5 comments

Comments

@lukeis
Copy link
Member

@lukeis lukeis commented Mar 4, 2016

Originally reported on Google Code with ID 7092

This error is thrown when calling the browser.close method

Errno::ECONNREFUSED: No connection could be made because the target machine actively
refused it. - connect(2)
        from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:762:in `initialize'
        from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:762:in `open'
        from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:762:in `block in connect'
        from C:/Ruby193/lib/ruby/1.9.1/timeout.rb:54:in `timeout'
        from C:/Ruby193/lib/ruby/1.9.1/timeout.rb:99:in `timeout'
        from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:762:in `connect'
        from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:755:in `do_start'
        from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:744:in `start'
        from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:1284:in `request'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.40.0/lib/selenium/webdriver/remote/http/default.rb:83:in
`response_for'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.40.0/lib/selenium/webdriver/remote/http/default.rb:39:in
`request'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.40.0/lib/selenium/webdriver/remote/http/common.rb:40:in
`call'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.40.0/lib/selenium/webdriver/remote/bridge.rb:634:in
`raw_execute'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.40.0/lib/selenium/webdriver/remote/bridge.rb:612:in
`execute'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.40.0/lib/selenium/webdriver/remote/bridge.rb:200:in
`quit'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.40.0/lib/selenium/webdriver/ie/bridge.rb:59:in
`quit'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.40.0/lib/selenium/webdriver/common/driver.rb:168:in
`quit'
        from C:/Ruby193/lib/ruby/gems/1.9.1/gems/watir-webdriver-0.6.8/lib/watir-webdriver/browser.rb:136:in
`close'
        from (irb):8
        from C:/Ruby193/bin/irb:12:in `<main>'

What steps will reproduce the problem?
1. Open up IRB
2. run require 'watir-webdriver'
3. Next run @browser = Watir::Browser.new :ie
4. Lastly run @browser.close
5. This error does not happen in Firefox or Chrome

What is the expected output? What do you see instead?
No error to be thrown

Selenium version: 2.40.0
OS: Windows 7 Home Premium x64
Browser: Internet Explorer
Browser version: 10

Reported by Natey24 on 2014-03-13 17:47:46

@lukeis
Copy link
Member Author

@lukeis lukeis commented Mar 4, 2016

Reported by barancev on 2014-03-13 19:38:06

  • Labels added: Lang-Ruby, Browser-IE
  • Labels removed: Status-Untriaged
@lukeis
Copy link
Member Author

@lukeis lukeis commented Mar 4, 2016

Is IEDriverServer.exe alive and listening when you attempt to call @browser.close? 

Reported by jari.bakken on 2014-03-14 10:04:39

  • Status changed: NeedsClarification
@lukeis
Copy link
Member Author

@lukeis lukeis commented Mar 4, 2016

Closing the issue due to inactivity.

Reported by barancev on 2014-04-20 20:31:17

  • Status changed: Invalid
@lukeis
Copy link
Member Author

@lukeis lukeis commented Mar 4, 2016

Reported by jari.bakken on 2015-02-26 23:02:13

@lukeis
Copy link
Member Author

@lukeis lukeis commented Mar 4, 2016

Reported by luke.semerau on 2015-09-17 18:22:12

  • Labels added: Restrict-AddIssueComment-Commit
@lukeis lukeis closed this Mar 4, 2016
@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Mar 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant