[selenium-users] Grid with InternetExplorerDriver hangs frequently and doesn't get its session killed

On Mon, May 21, 2012 at 11:37 PM, Ian Simpson wrote:

I started experimenting with using InternetExplorerDriver recently hoping
that my experience would be different than using it locally, and sadly it's
about the same.

When running it locally, I would frequently hit issues where the browser
would go into a state where it would just never respond back to my test.
Oddly enough, clicking on the hidden security certificate info box would
force it to return ready state, per my ticket in
http://code.google.com/p/selenium/issues/detail?id=1906.

I was hoping that this wouldn't be the case in Grid, since Grid is able to
detect sessions that have gone idle for too long and kill them. Not so, as
we're seeing the same issue happen constantly. Similarly, clicking on the
same hidden box in issue 1906 causes the browser to respond again.

Is InternetExplorerDriver just going to be unusable for us, or are there
better ways to manage it via Grid?

--
You received this message because you are subscribed to the Google Groups
"Selenium Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/selenium-users/-/sMH0g3ytvOEJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/selenium-users?hl=en.

On Tuesday, May 22, 2012 2:58:57 AM UTC-6, François Reynaud wrote:

Hi,

grid detects dead session, and sends a quit() command when that happens.
It's using the webdriver api to release resources. If IE is irresponsive,
grid won't help.
You could potentially plug in a tiemoutlistener hook(1), and do some magic
in there, but it might be more effort than fixing the root cause.

1- implement the timeout listener, and put something in there that really
frees the resources. Restart the node, kill the process.
thanks,
François.

On Monday, May 21, 2012 4:37:02 PM UTC-6, Ian Simpson wrote:

I started experimenting with using InternetExplorerDriver recently hoping
that my experience would be different than using it locally, and sadly it's
about the same.

When running it locally, I would frequently hit issues where the browser
would go into a state where it would just never respond back to my test.
Oddly enough, clicking on the hidden security certificate info box would
force it to return ready state, per my ticket in
http://code.google.com/p/selenium/issues/detail?id=1906.

I was hoping that this wouldn't be the case in Grid, since Grid is able to
detect sessions that have gone idle for too long and kill them. Not so, as
we're seeing the same issue happen constantly. Similarly, clicking on the
same hidden box in issue 1906 causes the browser to respond again.

Is InternetExplorerDriver just going to be unusable for us, or are there
better ways to manage it via Grid?

On Tuesday, May 22, 2012 7:42:45 AM UTC-7, Ian Simpson wrote:

I just realized I should probably provide more details. This is using
Internet Explorer 8 on a Windows 7 32-bit virtual machine with Selenium
2.21 and Grid 2.21.

Is IE9 any better when it comes to this sort of problem?

On Tuesday, May 22, 2012 12:57:04 PM UTC-6, ChaotX wrote:

I also see problems a long time ago with IE. My problem is that it also
kills the JVM so the entire machine disappear from grid. It usually occure
after a login to the site, so we neither able to use IE for auto tests. :(

On Tuesday, May 22, 2012 2:45:34 PM UTC-6, Jim Evans wrote:

Would a page load timeout help you here? One has been implemented for IE
for the forthcoming 2.22 release.

On Tuesday, May 22, 2012 4:07:02 AM UTC+5:30, Ian Simpson wrote:

I started experimenting with using InternetExplorerDriver recently hoping
that my experience would be different than using it locally, and sadly it's
about the same.

When running it locally, I would frequently hit issues where the browser
would go into a state where it would just never respond back to my test.
Oddly enough, clicking on the hidden security certificate info box would
force it to return ready state, per my ticket in
http://code.google.com/p/selenium/issues/detail?id=1906.

I was hoping that this wouldn't be the case in Grid, since Grid is able to
detect sessions that have gone idle for too long and kill them. Not so, as
we're seeing the same issue happen constantly. Similarly, clicking on the
same hidden box in issue 1906 causes the browser to respond again.

Is InternetExplorerDriver just going to be unusable for us, or are there
better ways to manage it via Grid?