search

ericmckean / chromedriver

Automatically exported from code.google.com/p/chromedriver
0 stars 0 forks source link

No buffer space available #1000

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
After upgrading to chromedriver v2.12 from 2.10 I started getting this error 
about about half an hour into the test run. I went back and tried chromedriver 
2.11 and this error was present in that version as well.

I'm using vaadin testbench for the which is built on webdriver 2.40.

org.openqa.selenium.remote.UnreachableBrowserException: Error communicating 
with the remote browser. It may have died.
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: host: '6KM19W1-L', ip: '172.24.32.64', os.name: 'Windows 7', 
os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_55'
Driver info: driver.version: RemoteWebDriver
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:567) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.openqa.selenium.remote.RemoteWebDriver.executeScript(RemoteWebDriver.java:482) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at com.vaadin.testbench.commands.TestBenchCommandExecutor.waitForVaadin(TestBenchCommandExecutor.java:137) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at com.vaadin.testbench.CachedInvocationHandler.waitForVaadinIfNecessary(CachedInvocationHandler.java:88) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at com.vaadin.testbench.CachedInvocationHandler.invoke(CachedInvocationHandler.java:50) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at com.sun.proxy.$Proxy16.findElement(Unknown Source) ~[?:?]
    at com.fireapps.pages.AbstractPage.navigateTo(AbstractPage.java:105) [bin/:?]
    at com.fireapps.pages.ProcessingHistory.navigateTo(ProcessingHistory.java:25) [bin/:?]
    at com.fireapps.tests.importerror.ImportError.runImport(ImportError.java:99) [bin/:?]
    at com.fireapps.tests.importerror.ImportError.runImport(ImportError.java:76) [bin/:?]
    at com.fireapps.tests.importerror.ImportErrorTestV2.test_v2_hedgeappend(ImportErrorTestV2.java:72) [bin/:?]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.7.0_55]
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_55]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_55]
    at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.7.0_55]
    at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) [testng.jar:6.8.7beta-201309140723]
    at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) [testng.jar:6.8.7beta-201309140723]
    at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) [testng.jar:6.8.7beta-201309140723]
    at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) [testng.jar:6.8.7beta-201309140723]
    at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) [testng.jar:6.8.7beta-201309140723]
    at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) [testng.jar:6.8.7beta-201309140723]
    at org.testng.TestRunner.privateRun(TestRunner.java:767) [testng.jar:6.8.7beta-201309140723]
    at org.testng.TestRunner.run(TestRunner.java:617) [testng.jar:6.8.7beta-201309140723]
    at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) [testng.jar:6.8.7beta-201309140723]
    at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) [testng.jar:6.8.7beta-201309140723]
    at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) [testng.jar:6.8.7beta-201309140723]
    at org.testng.SuiteRunner.run(SuiteRunner.java:240) [testng.jar:6.8.7beta-201309140723]
    at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) [testng.jar:6.8.7beta-201309140723]
    at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) [testng.jar:6.8.7beta-201309140723]
    at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224) [testng.jar:6.8.7beta-201309140723]
    at org.testng.TestNG.runSuitesLocally(TestNG.java:1149) [testng.jar:6.8.7beta-201309140723]
    at org.testng.TestNG.run(TestNG.java:1057) [testng.jar:6.8.7beta-201309140723]
    at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111) [testng.jar:6.8.7beta-201309140723]
    at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204) [testng.jar:6.8.7beta-201309140723]
    at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175) [testng.jar:6.8.7beta-201309140723]
Caused by: org.openqa.selenium.WebDriverException: java.net.SocketException: No 
buffer space available (maximum connections reached?): connect
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: host: '6KM19W1-L', ip: '172.24.32.64', os.name: 'Windows 7', 
os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_55'
Driver info: driver.version: RemoteWebDriver
    at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:75) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:546) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    ... 34 more
Caused by: java.net.SocketException: No buffer space available (maximum 
connections reached?): connect
    at java.net.DualStackPlainSocketImpl.connect0(Native Method) ~[?:1.7.0_55]
    at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) ~[?:1.7.0_55]
    at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) ~[?:1.7.0_55]
    at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) ~[?:1.7.0_55]
    at java.net.AbstractPlainSocketImpl.connect(Unknown Source) ~[?:1.7.0_55]
    at java.net.PlainSocketImpl.connect(Unknown Source) ~[?:1.7.0_55]
    at java.net.SocksSocketImpl.connect(Unknown Source) ~[?:1.7.0_55]
    at java.net.Socket.connect(Unknown Source) ~[?:1.7.0_55]
    at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:117) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:178) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:319) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:298) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:66) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:546) ~[vaadin-testbench-standalone-3.1.3.jar:?]
    ... 34 more

Original issue reported on code.google.com by mitchel...@gmail.com on 10 Dec 2014 at 8:29

GoogleCodeExporter commented 9 years ago 
Do you have ready to run codes that can reproduce problem?  - prefer small 
program.

Original comment by andrewch...@chromium.org on 10 Dec 2014 at 10:39

GoogleCodeExporter commented 9 years ago 
No, unfortunately the buffer space is exceeded sometime between ~30-60min into 
execution the test suite. It does not seem to be associated with any specific 
action. I have a chromedriver log of the test run, though there does not seem 
to be anything immediately obvious within.

Original comment by mitchel...@gmail.com on 10 Dec 2014 at 11:48

GoogleCodeExporter commented 9 years ago 
In the latest version (2.13) the following additional message is logged to the 
console.

Dec 22, 2014 10:24:24 AM org.openqa.selenium.os.UnixProcess$SeleniumWatchDog 
destroyHarder
INFO: Command failed to close cleanly. Destroying forcefully (v2). 
org.openqa.selenium.os.UnixProcess$SeleniumWatchDog@20cb0003

Original comment by mitchel...@gmail.com on 22 Dec 2014 at 6:31

GoogleCodeExporter commented 9 years ago

Original comment by samu...@chromium.org on 21 Feb 2015 at 12:18