I have been attempting to launch multiple Node instances using the Chrome webdriver on an Amazon EC2 server. However, I have encountered a problem where once I reach a total of 84 node instances, Selenium throws an error:
Build information: version: '2.44.0', revision: '76d78cf', timestamp: '2014-10-23 20:02:37'
System information: host: 'ip-172-31-25-40', ip: '127.0.0.1', operating system name: 'Linux', architecture: 'amd64', version: '3.2.0-60-virtual', Java version: '1.7.0_65'
Driver information: driver version: unknown
at org.openqa.selenium.remote.server.DefaultDriverProvider.callConstructor(DefaultDriverProvider.java:69)
at org.openqa.selenium.remote.server.DefaultDriverProvider.newInstance(DefaultDriverProvider.java:53)
at org.openqa.selenium.remote.server.DefaultDriverFactory.newInstance(DefaultDriverFactory.java:54)
at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:214)
at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:168)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedConstructorAccessor12.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.openqa.selenium.remote.server.DefaultDriverProvider.callConstructor(DefaultDriverProvider.java:59)
... 9 more
Caused by: org.openqa.selenium.WebDriverException: Unknown error: Chrome failed to start: exited abnormally
(Driver info: chromedriver=2.12.301324 (de8ab311bc9374d0ade71f7c167bad61848c7c48), platform=Linux 3.2.0-60-virtual x86_64) (WARNING: The server did not provide any stacktrace information)
I initially suspected that the issue might be related to my ulimit -n setting being set to 1024, but even after changing it to 65K, the problem persisted. Any insights from experienced users would be greatly appreciated.