selenium-google-code-issue-archive icon indicating copy to clipboard operation
selenium-google-code-issue-archive copied to clipboard

selenium grid2 starting too many chrome processes

Open lukeis opened this issue 8 years ago • 6 comments

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)_

lukeis avatar Mar 04 '16 08:03 lukeis

Do you call driver.quit() to close sessions?

Reported by barancev on 2014-07-21 19:21:38

  • Status changed: NeedsClarification
  • Labels added: Browser-Chrome

lukeis avatar Mar 04 '16 08:03 lukeis

I am using watir-webdriver and i call @browser.driver.quit
All the webdriver instances are closed individually as soon as they are completed.

This could be related to https://code.google.com/p/selenium/issues/detail?id=6811 that
when creating a webdriver failed/crashed, the browsers created are not killed.

Reported by eelam.ragavan on 2014-07-22 12:02:07

lukeis avatar Mar 04 '16 08:03 lukeis

Reported by barancev on 2014-07-23 08:30:24

  • Labels added: Lang-Ruby

lukeis avatar Mar 04 '16 08:03 lukeis

I don't see anything Ruby-specific here. The fact that it works well with Firefox points
to a Chrome (or Chrome+Grid) issue.

Reported by jari.bakken on 2014-07-23 09:44:47

  • Status changed: New
  • Labels removed: Lang-Ruby

lukeis avatar Mar 04 '16 08:03 lukeis

Ah, sorry. I missed mention of the grid.

Reported by barancev on 2014-07-23 11:49:37

  • Labels added: Component-Grid

lukeis avatar Mar 04 '16 08:03 lukeis

Reported by luke.semerau on 2015-09-17 17:47:04

  • Labels added: Restrict-AddIssueComment-Commit

lukeis avatar Mar 04 '16 08:03 lukeis