Closing threads

[Marcel Overdijk]

I'm running WebDriverBackedSelenium in fitnesse ut I have some problem
with threads.
The fitnesse tests never terminate due the fact a thread keeps
running.

I guess webdriver/selenium strarts a separate thread when starting a
new browser.
My fitnesse fixture code calling "stop" on the selenium instance, but
somehow a thread keeps running.

Do you have any idea if this could be due to webdriver/selenium?

[Marcel Overdijk]

To be more precise I did some debugging and after I invoke
selenium.stop() from fitnesse, the thread below keeps running:

- Thread [pool-2-Thread-1] (Running)
- Daemon Thread [MultiThreadedHttpConnectionManager cleanup]
(Running)

I think this is started by selenium but not closes.

Is this a bug in Selenium 2.0 a1 or am I doing something wrong?

[Marcel Overdijk]

Possibly the embedded selenium server is not stopped?

[Simon Stewart]

There's no embedded selenium server when using the webdriver-backed
selenium, but we do fire up a watchdog thread to allow us to time out
commands. That probably needs some tidy up.

Simon

On Wed, Dec 16, 2009 at 5:16 AM, Marcel Overdijk
<marcelo...@gmail.com> wrote:
> Possibly the embedded selenium server is not stopped?
>

> --
>
> You received this message because you are subscribed to the Google Groups "webdriver" group.
> To post to this group, send email to webd...@googlegroups.com.
> To unsubscribe from this group, send email to webdriver+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/webdriver?hl=en.
>
>
>

[Marcel Overdijk]

OK. This is currently a blocker to continue to work on integrating
webdriver/selenium 2.0 in fitnesse fixtures.
I will follow the release plan of selenium 2.0 I try to some
integration in the future.

If you find something related to closing threads during the
development process of selenium 2.0, perhaps you can keep me posted in
this thread.

[Simon Stewart]

It's a pretty easy fix and should be in the next alpha release of selenium 2.

Simon

[Marcel Overdijk]

Sounds great. Thanks for the update.

When will the next alpha release be released?

[Simon Stewart]

Good question. There's a blindingly obvious problem in the
SeleniumServer to do with the remote webdriver that I've fixed, but
I'd like to get some clean up done around the chrome driver before
doing another release. Is there anything that the other devs would
expect to see if there?

Simon

[Simon Stewart]

This should have addressed the issue, assuming you call "selenium.stop()":

http://code.google.com/p/selenium/source/detail?r=7910

Simon