What is expected behavior for native/non-intermediary webdrivers after initiating selenium process ends?

[じょいすじょん]

What is the expected behavior for native or non-intermediary webdriver implementations after the session initiating Selenium language bindings' process ends?

For example a session in Python, if the Python process is killed or crashes or ends normally, but fails to send the quit command to the WebDriver, should the WebDriver process remain running, terminate immediately, or terminate after some period of inactivity?

[Luke Inman-Semerau]

For the most part selenium relies on the user to ensure quit is called, so in those cases the driver would remain running indefinitely. The only exception is with Grid, where timeouts are configurable to quit sessions after a period of time of inactivity. 

-Luke

On Jul 19, 2016, at 7:21 AM, じょいすじょん <dangerwillro...@gmail.com> wrote:

What is the expected behavior for native or non-intermediary webdriver implementations after the session initiating Selenium language bindings' process ends?

For example a session in Python, if the Python process is killed or crashes or ends normally, but fails to send the quit command to the WebDriver, should the WebDriver process remain running, terminate immediately, or terminate after some period of inactivity?

--
You received this message because you are subscribed to the Google Groups "Selenium Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-developers/9b94c0d7-601c-4fe6-8604-1638562eb0e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.