This repository was archived by the owner on Nov 29, 2018. It is now read-only.
This repository was archived by the owner on Nov 29, 2018. It is now read-only.
selenium grid2 starting too many chrome processes #7619
Open
Description
Originally reported on Google Code with ID 7619
selenium-webdriver : 2.41.0
nodes running on AWS c3.xlarge (8GB mem, 4 cpu)
OS info: 3.10.40-50.136.amzn1.x86_64 #1 SMP Tue May 13 21:35:08 UTC 2014 x86_64 x86_64
x86_64 GNU/Linux
Chrome: 35, Chromedriver 2.10 64bit
I have 5 aws nodes each having 25 chrome/firefox
I am able to successfully run test against FF on all nodes in parallel with 20+ of
ff instances are running at the same time.
But when it comes to chrome, barely after 10 chrome instances are open, i get OutOfMemory/Timeouts
1) ps -ef | grep chrome , shows lots of chrome related processes are running even after
all tests are completed. (o/p attached)
2) after the test is run, chromedriver binary is still seen running. This is supposed
to be stopped i assume after all runs are completed
Reported by eelam.ragavan
on 2014-07-17 10:02:08
- _Attachment: [chrome_processes.txt](https://storage.googleapis.com/google-code-attachments/selenium/issue-7619/comment-0/chrome_processes.txt)_