getText() can fail on 'found' element with InterruptedException

[lukeis]

Originally reported on Google Code with ID 2913

Se 2.13 & Firefox 3.6.23

I'll work towards a reproduction, but here is a stack trace on the RemoteWebDriver
side of a divide:

java.lang.InterruptedException
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(Unknown
Source)
    at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
    at java.util.concurrent.FutureTask.get(Unknown Source)
    at org.openqa.selenium.remote.server.DefaultSession.execute(DefaultSession.java:139)
    at org.openqa.selenium.remote.server.handler.WebDriverHandler.handle(WebDriverHandler.java:44)
    at org.openqa.selenium.remote.server.rest.ResultConfig.handle(ResultConfig.java:188)
    at org.openqa.selenium.remote.server.DriverServlet.handleRequest(DriverServlet.java:573)
    at org.openqa.selenium.remote.server.DriverServlet.doGet(DriverServlet.java:503)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
    at org.openqa.selenium.remote.server.DriverServlet.service(DriverServlet.java:477)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.openqa.jetty.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
    at org.openqa.jetty.jetty.servlet.ServletHandler.dispatch(ServletHandler.java:677)
    at org.openqa.jetty.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
    at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1530)
    at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1482)
    at org.openqa.jetty.http.HttpServer.service(HttpServer.java:909)
    at org.openqa.jetty.http.HttpConnection.service(HttpConnection.java:820)
    at org.openqa.jetty.http.HttpConnection.handleNext(HttpConnection.java:986)
    at org.openqa.jetty.http.HttpConnection.handle(HttpConnection.java:837)
    at org.openqa.jetty.http.SocketListener.handleConnection(SocketListener.java:243)
    at org.openqa.jetty.util.ThreadedServer.handle(ThreadedServer.java:357)
    at org.openqa.jetty.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

The page in question is part static, and par dynamic (automatically loading immediately
after the initial page load).

The widget in question is found during the initial page load, but modified (somehow)
by the async stage.  findElement works just fine (with a waitFor).  getText() fails,
and one the browser side issues the exception above.  

By the time the exception arrives over the wire to the test-script side, it's been
wrapped in a totally generic WebDriverException.

- Paul

Reported by paul@hammant.org on 2011-11-22 22:42:50

[lukeis]

Reported by barancev on 2011-11-23 10:07:19

• Labels added: Component-WebDriver, Lang-Java

[lukeis]

This seems to happen not only on getText requests but also other situations.
Here's an occurrence of it during findElement:

10:15:24.843 INFO - Executing: [find element: By.selector: .automation-phone] at URL:
/session/1332436487875/element)
10:15:24.843 WARN - Exception thrown
java.lang.InterruptedException
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(Unknown
Source)
    at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
    at java.util.concurrent.FutureTask.get(Unknown Source)
    at org.openqa.selenium.remote.server.DefaultSession.execute(DefaultSession.java:139)
    at org.openqa.selenium.remote.server.handler.WebDriverHandler.handle(WebDriverHandler.java:44)
    at org.openqa.selenium.remote.server.rest.ResultConfig.handle(ResultConfig.java:196)
    at org.openqa.selenium.remote.server.DriverServlet.handleRequest(DriverServlet.java:577)
    at org.openqa.selenium.remote.server.DriverServlet.doPost(DriverServlet.java:528)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at org.openqa.selenium.remote.server.DriverServlet.service(DriverServlet.java:500)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.openqa.jetty.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
    at org.openqa.jetty.jetty.servlet.ServletHandler.dispatch(ServletHandler.java:677)
    at org.openqa.jetty.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
    at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1530)
    at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1482)
    at org.openqa.jetty.http.HttpServer.service(HttpServer.java:909)
    at org.openqa.jetty.http.HttpConnection.service(HttpConnection.java:820)
    at org.openqa.jetty.http.HttpConnection.handleNext(HttpConnection.java:986)
    at org.openqa.jetty.http.HttpConnection.handle(HttpConnection.java:837)
    at org.openqa.jetty.http.SocketListener.handleConnection(SocketListener.java:243)
    at org.openqa.jetty.util.ThreadedServer.handle(ThreadedServer.java:357)
    at org.openqa.jetty.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
10:15:24.843 WARN - Exception: null
10:15:25.359 INFO - Command request: captureScreenshot[c:\job_assets\shot_18.png, ]
on session 1332436487875
10:15:25.718 INFO - Got result: OK on session 1332436487875

Platform info:

10:14:47.531 INFO - Java: Sun Microsystems Inc. 20.6-b01
10:14:47.531 INFO - OS: Windows XP 5.1 x86
10:14:47.609 INFO - v2.18.0, with Core v2.18.0. Built from revision 15704

Reported by santiycr on 2012-03-22 18:26:26

[lukeis]

v2.20 of Selenium - right Santiago?

I'm also seeing StaleElementReferenceException similarly failing.  I mean Failing on
the getText() immediately following a lookup.  Refer http://stackoverflow.com/questions/4846454/selenium-webdriver-staleelementreferenceexception
and similar.

Reported by paul@hammant.org on 2012-03-22 18:30:56

[lukeis]

Still haven't gotten of report of a user using 2.20.0, but I'd be surprised if it's
not there as I didn't see any commits related to this issue in the changelog.
Paul, did you repro in 2.20.0?

Reported by santiycr on 2012-03-22 18:41:12

[lukeis]

At the bottom of http://code.google.com/p/selenium/issues/detail?id=2915 I have a script
that reproduces that one publically, and the issue is still in there for 2.20.  I feel
they are related somehow.

Reported by paul@hammant.org on 2012-03-22 18:56:02

[lukeis]

With v2.20, I think the issue now manifests itself as:

    WebDriverException: Unable to get element text ...

All we did is findElement(id("foo")).getText(), and it barfs for out JavaServerFaces
app 1/4.  

If we slow the test down, or employ one of the waitFor strategies we can overcome it,
but it's curious.  The Element in question is not written dynamically.  The browser
is not slow (it, the runner, the tomcat instance, and the embedded H2 database are
all localhost). The machine is not resource constrained.

Reported by paul@hammant.org on 2012-03-22 21:51:34

[lukeis]

OK, so the "Unable to get element text" is IE only (GetElementTextCommandHandler.h,
line 75). 

Reported by paul@hammant.org on 2012-03-23 14:23:00