FAQ
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 selenium-users@googlegroups.com.
To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.

Search Discussions

  • François Reynaud at May 22, 2012 at 8:59 am
    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 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 selenium-users@googlegroups.com.
    To unsubscribe from this group, send email to
    selenium-users+unsubscribe@googlegroups.com.
    For more options, visit this group at
    http://groups.google.com/group/selenium-users?hl=en.
    --
    You received this message because you are subscribed to the Google Groups "Selenium Users" group.
    To post to this group, send email to selenium-users@googlegroups.com.
    To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
  • Ian Simpson at May 22, 2012 at 3:17 pm
    Gotcha; it makes sense that if it's not responsive a call to quit()
    wouldn't help either.

    Part of the problem is that we don't know what's causing IE to be
    unresponsive. The page loads and then... nothing. This happens constantly.

    I'm curious if IE9 plays better in this regard. If not then I think it's
    totally unusable for our automation since we would end up killing the
    browser early in almost every test case.
    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 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 selenium-users@googlegroups.com.
    To unsubscribe from this group, send email to
    selenium-users+unsubscribe@googlegroups.com.
    For more options, visit this group at
    http://groups.google.com/group/selenium-users?hl=en.
    --
    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/-/ckrsB9dDzewJ.
    To post to this group, send email to selenium-users@googlegroups.com.
    To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
  • Ian Simpson at May 22, 2012 at 2:42 pm
    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 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?
    --
    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/-/h8z2D9_gr8wJ.
    To post to this group, send email to selenium-users@googlegroups.com.
    To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
  • Mike Riley at May 22, 2012 at 4:33 pm
    I am seeing something similar in my situation, although I am using an older
    version of Selenium. In my case I was seeing some Java runtime errors as
    well, but not always. I often end up with an orphaned IE browser.

    Like you I am using IE 9 32-bit on Win 7, but my Win 7 is 64-bit. Not sure
    if that matters. I am also running these through Grid2 and it sometimes
    hoses the Grid2 hub when it happens.

    Mike
    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 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?
    --
    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/-/LjnyA1EN5sYJ.
    To post to this group, send email to selenium-users@googlegroups.com.
    To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
  • ChaotX at May 22, 2012 at 6:57 pm
    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. :(

    --
    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/-/BZZ0hbw7lqwJ.
    To post to this group, send email to selenium-users@googlegroups.com.
    To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
  • Ian Simpson at May 22, 2012 at 8:39 pm
    So I just tried installing IE9 on the machine instead, and unfortunately I
    hadn't considered before hand "In what ways could IE9 actually make this
    problem *worse..."*
    *
    *
    Before if I interacted with IE8 in such a way as to generate a modal
    dialog, it would force ready state to be returned to the driver. Now, with
    IE9, when I interact in that way, it causes a new window to be opened, and
    each new window requires you interact with it, opening new windows until
    you don't have enough system resources/sanity left.

    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. :(
    --
    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/-/t4eiLVMno8kJ.
    To post to this group, send email to selenium-users@googlegroups.com.
    To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
  • Jim Evans at May 22, 2012 at 8:45 pm
    Would a page load timeout help you here? One has been implemented for IE for the forthcoming 2.22 release.

    --
    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/-/QjSy5pWboJUJ.
    To post to this group, send email to selenium-users@googlegroups.com.
    To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
  • Ian Simpson at May 22, 2012 at 10:50 pm
    Potentially; it depends how it works though.

    If we're just talking about timeouts when issuing a get(), then that only
    solves part of the problem. If it also works for clicking links,
    submitting forms, etc, then it sounds like it would work if it effectively
    forces the driver instance to return after a certain amount of time.
    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.
    --
    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/-/auECbZdMi4gJ.
    To post to this group, send email to selenium-users@googlegroups.com.
    To unsubscribe from this group, send email to selenium-users+unsubscribe@googlegroups.com.
    For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
  • Aryasindhu Sahu at Oct 21, 2013 at 11:37 am
    Hi Ian,

    try deleting the Temp files of the System running NODE. It helped for me.


    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?
    --
    You received this message because you are subscribed to the Google Groups "Selenium Users" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to selenium-users+unsubscribe@googlegroups.com.
    To post to this group, send email to selenium-users@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/adbeeb60-8dde-4af1-b382-acd5a3940047%40googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupselenium-users @
categoriesselenium
postedMay 21, '12 at 10:37p
activeOct 21, '13 at 11:37a
posts10
users6
websiteseleniumhq.org

People

Translate

site design / logo © 2022 Grokbase