Re: Issue 4761 in selenium: IDE/Core: can't access dead object error

[sele...@googlecode.com]

Updates:
Summary: IDE/Core: can't access dead object error

Comment #2 on issue 4761 by luke.semerau: IDE/Core: can't access dead
object error
http://code.google.com/p/selenium/issues/detail?id=4761

relevant post with many Se users complaining of the same / similar problem
in IDE
http://blog.mozilla.org/addons/2012/09/12/what-does-cant-access-dead-object-mean/

[sele...@googlecode.com]

Comment #3 on issue 4761 by luke.semerau: IDE/Core: can't access dead
object error
http://code.google.com/p/selenium/issues/detail?id=4761

Issue 4983 has been merged into this issue.

[sele...@googlecode.com]

Comment #4 on issue 4761 by barancev: IDE/Core: can't access dead object
error
http://code.google.com/p/selenium/issues/detail?id=4761

Issue 4710 has been merged into this issue.

[sele...@googlecode.com]

Comment #5 on issue 4761 by george.h...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

Seeing very similar behaviour with Selenium IDE 1.10.0 installed to Firefox
18.0.2 on Windows. Anyone know of a workaround to this?

Best regards,
George


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[sele...@googlecode.com]

Comment #6 on issue 4761 by m...@guttman.co.il: IDE/Core: can't access dead
object error
http://code.google.com/p/selenium/issues/detail?id=4761

The attached file results in:
[info] Executing: |open |
/Eng/MarketData/Indices/MarketCap/Pages/IndexHistoryData.aspx?Action=1&addTab=&IndexId=142
| |
[info] Executing: |click | id=history1 | |
[info] Executing: |clickAndWait | xpath=(//input[@value='Display
Data'])[2] | |
[info] Executing: |click | css=td.GreenTextBtn | |
[info] Executing: |click | link=TSV | |
[warn] Opening window '_blank', which is not a real window name.
Randomizing target to be: selenium_blank35973
[info] Executing: |waitForPopUp | _blank | 30000 |
[error] can't access dead object

FF 18.0.2 on an up-to-date Windows 7 (64 bit)

Attachments:
TASE_eng.html 1.1 KB

[sele...@googlecode.com]

Updates:
Cc: simon.m.stewart

Comment #7 on issue 4761 by barancev: IDE/Core: can't access dead object
error
http://code.google.com/p/selenium/issues/detail?id=4761

(No comment was entered for this change.)

[sele...@googlecode.com]

Comment #8 on issue 4761 by Locr...@gmail.com: IDE/Core: can't access dead
object error
http://code.google.com/p/selenium/issues/detail?id=4761

I am using Selenium Server 2.30 and FF 18.0.1 and am also encountering
the "Can't access dead object" error while waiting for page after a button
click.

[sele...@googlecode.com]

Comment #9 on issue 4761 by rafalfu...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

when will the fix be available?

[sele...@googlecode.com]

Comment #10 on issue 4761 by idealbo...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

Rolling back to Firefox 12.0 fixes the issue

[sele...@googlecode.com]

Comment #11 on issue 4761 by barancev: IDE/Core: can't access dead object
error
http://code.google.com/p/selenium/issues/detail?id=4761

Issue 5364 has been merged into this issue.

[sele...@googlecode.com]

Comment #12 on issue 4761 by discordi...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

I'm using java selenium client 2.31.0 and FF 18.0.2 (webdriver) on windows
7 and I'm also run into this bug from time to time. No popup windows
however, it's just a click on a link that sometimes causes the following
error:

Error: can't access dead object
Source:
file:///C:/Users/user/AppData/Local/Temp/anonymous8144928914942444972webdriver-profile/extensions/fxdr...@googlecode.com/components/driver_component.js
Line: 8226

driver_component.js:
8216 e.setUserData("webdriver-evaluate-code", null, null);
8217 a.send()
8218 }
8219 };
8220 e.addEventListener("webdriver-evaluate-response", j, !0);
8221 b = e.createEvent("Events");
8222 b.initEvent("webdriver-evaluate", !0, !1);
8223 e.dispatchEvent(b)
8224 };
8225 d.runWhenTrue(function() {
8226 return!!e.body
8227 }, function() {
8228 if(!e.getUserData("webdriver-evaluate-attached")) {
8229 var a = e.createElement("script");
8230 a.setAttribute("type", "text/javascript");
8231 a.innerHTML = FirefoxDriver.listenerScript;
8232 e.body.appendChild(a);
8233 a.parentNode.removeChild(a)
8234 }
8235 d.runWhenTrue(l, k, 1E4, p)
8236 }, 1E4, function() {

[sele...@googlecode.com]

Comment #13 on issue 4761 by rafalfu...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

--> Rolling back to Firefox 12.0 fixes the issue
Yes, Its working with FF14 too, but i would like to upgrade firefox to the
latest.
Anyone know any workaround or a temp fix for this issue?

[sele...@googlecode.com]

Comment #14 on issue 4761 by mguttm...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

A quote from the Firefox "Addons"
L<https://blog.mozilla.org/addons/2012/09/12/what-does-cant-access-dead-object-mean/>
blog:

Firefox 15 introduced a major improvement in memory usage, by disallowing
add-ons to keep references to DOM objects after their parent document was
destroyed. This eliminates the most common cause of memory leaks in
add-ons, and should reduce memory consumption for many users.

*******

This means that Firefox did the right thing and prevented the add-on from
holding on to this object. However, it also means that the add-on probably
won’t work correctly.

Please note the last sentence...

FYI!

[sele...@googlecode.com]

Comment #15 on issue 4761 by mguttm...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

A quote from the Firefox "Addons" blog
(https://blog.mozilla.org/addons/2012/09/12/what-does-cant-access-dead-object-mean/):

Firefox 15 introduced a major improvement in memory usage, by disallowing
add-ons to keep references to DOM objects after their parent document was
destroyed. This eliminates the most common cause of memory leaks in
add-ons, and should reduce memory consumption for many users.

snip ******* snip

[sele...@googlecode.com]

Comment #16 on issue 4761 by hippy...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

Still a problem in the latest release of webdriver. Any workarounds for
this other than resurrecting ancient Firefox versions?

[sele...@googlecode.com]

Comment #17 on issue 4761 by rafalfu...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

i'd like to know it too @hippy

[sele...@googlecode.com]

Comment #18 on issue 4761 by zepedro....@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

Any progress on this?

[sele...@googlecode.com]

Comment #19 on issue 4761 by hippy...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

Anyone got any further? I'm looking really stupid to a lot of people who
say that testing is a pointless waste of time.

From my guess, the problem is that selenium needs to be able to rescan the
document and pick up the fact that the dom object it had cached with an
id/selector of X has been replaced with another one, that has the same
id/selector. It looks like it caches the reference to it - hence Firefox
saying no. At least, that's what my research suggests - this is making any
test impossible to run, I can't believe such a major breaking problem that
affects every way I try to use selenium to test this page - PHPUnit, IDE,
htmlsuite - hasn't even had an acknowledgment yet - am I missing a fix
somewhere else that people are keeping to themselves?

[sele...@googlecode.com]

Comment #20 on issue 4761 by hippy...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

Ok, more info - it even happening if I open a page.

So my theory is totally wrong. It can't even abort the current page and
open a new one. This is a nightmare. Anyone got any ideas?

[sele...@googlecode.com]

Comment #21 on issue 4761 by hippy...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

Ok, more info - it even happening if I open a page.

So my theory is totally wrong. It can't even abort the current page and
open a new one. This is a nightmare. Anyone got any ideas?

16:01:34.585 INFO - Command request: isElementPresent[id=Address1, ] on
session 1458fc47064c4def93cf98c98a8771c7
16:01:34.589 INFO - Got result: OK,true on session
1458fc47064c4def93cf98c98a8771c7
16:01:34.590 INFO - Command request: getExpression[id=Address1, ] on
session 1458fc47064c4def93cf98c98a8771c7
16:01:34.594 INFO - Got result: OK,id=Address1 on session
1458fc47064c4def93cf98c98a8771c7
16:01:34.595 INFO - Command request: getValue[id=Address1, ] on session
1458fc47064c4def93cf98c98a8771c7
16:01:34.599 INFO - Got result: OK,1 The Street on session
1458fc47064c4def93cf98c98a8771c7
16:01:42.313 INFO - Command request: getExpression[name=save_details, ] on
session 1458fc47064c4def93cf98c98a8771c7
16:01:42.322 INFO - Got result: OK,name=save_details on session
1458fc47064c4def93cf98c98a8771c7
16:01:42.323 INFO - Command request: getExpression[name=save_details, ] on
session 1458fc47064c4def93cf98c98a8771c7
16:01:42.330 INFO - Got result: OK,name=save_details on session
1458fc47064c4def93cf98c98a8771c7
16:01:42.331 INFO - Command request: isElementPresent[name=save_details, ]
on session 1458fc47064c4def93cf98c98a8771c7
16:01:42.351 INFO - Got result: OK,true on session
1458fc47064c4def93cf98c98a8771c7
16:01:43.216 INFO - Command request: getExpression[id=AccountNo, ] on
session 1458fc47064c4def93cf98c98a8771c7
16:01:43.223 INFO - Got result: OK,id=AccountNo on session
1458fc47064c4def93cf98c98a8771c7
16:01:43.226 INFO - Command request: getValue[id=AccountNo, ] on session
1458fc47064c4def93cf98c98a8771c7
16:01:43.232 INFO - Got result: OK,CUSTID on session
1458fc47064c4def93cf98c98a8771c7
16:01:49.951 INFO - Command request:
getExpression[/MY/APP/contacts/edit/cus/CUSTID, ] on session
1458fc47064c4def93cf98c98a8771c7
16:01:49.958 INFO - Got result: OK,/vision/contacts/edit/cus/CUSTID on
session 1458fc47064c4def93cf98c98a8771c7
16:01:49.961 INFO - Command request: open[/vision/contacts/edit/cus/CUSTID,
] on session 1458fc47064c4def93cf98c98a8771c7
16:01:49.966 INFO - Got result: ERROR: Command execution failure. Please
search the user group at
https://groups.google.com/forum/#!forum/selenium-users for error details
from the log window. The error message is: can't access dead object on
session 1458fc47064c4def93cf98c98a8771c7
16:01:49.968 INFO - Command request: testComplete[, ] on session
1458fc47064c4def93cf98c98a8771c7
16:01:49.968 INFO - Killing Firefox...
16:01:50.176 INFO - Got result: OK on session
1458fc47064c4def93cf98c98a8771c7

[sele...@googlecode.com]

Comment #22 on issue 4761 by hippy...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

Ok, more info - it even happening if I open a page.

So my theory is totally wrong. It can't even abort the current page and
open a new one. This is a nightmare. Anyone got any ideas?

PHPUnit commands:

$this->waitForTextPresent("Company Info");
$this->assertElementPresent("id=Name");
$this->assertEquals("! selenium test customer",
$this->getValue("id=Name"));
$this->assertElementPresent("id=Address1");
$this->assertEquals("1 The Street", $this->getValue("id=Address1"));
$contactId = $this->getValue('id=AccountNo');
$this->open('/APPURL/contacts/edit/cus/' . $contactId);

------------

Console output:

16:09:49.181 INFO - Command request: getExpression[id=Name, ] on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.188 INFO - Got result: OK,id=Name on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.190 INFO - Command request: getExpression[id=Name, ] on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.195 INFO - Got result: OK,id=Name on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.197 INFO - Command request: isElementPresent[id=Name, ] on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.203 INFO - Got result: OK,true on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.205 INFO - Command request: getExpression[id=Name, ] on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.210 INFO - Got result: OK,id=Name on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.213 INFO - Command request: getValue[id=Name, ] on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.222 INFO - Got result: OK,! selenium test customer on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.226 INFO - Command request: getExpression[id=Address1, ] on
session 88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.231 INFO - Got result: OK,id=Address1 on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.232 INFO - Command request: getExpression[id=Address1, ] on
session 88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.236 INFO - Got result: OK,id=Address1 on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.237 INFO - Command request: isElementPresent[id=Address1, ] on
session 88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.240 INFO - Got result: OK,true on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.242 INFO - Command request: getExpression[id=Address1, ] on
session 88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.246 INFO - Got result: OK,id=Address1 on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.247 INFO - Command request: getValue[id=Address1, ] on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.251 INFO - Got result: OK,1 The Street on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.252 INFO - Command request: getExpression[id=AccountNo, ] on
session 88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.256 INFO - Got result: OK,id=AccountNo on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.257 INFO - Command request: getValue[id=AccountNo, ] on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.262 INFO - Got result: OK,CUSTID on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.263 INFO - Command request:
getExpression[/APPURL/contacts/edit/cus/CUSTID, ] on session
88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.267 INFO - Got result: OK,/APPURL/contacts/edit/cus/CUSTID on
session 88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.268 INFO - Command request: open[/APPURL/contacts/edit/cus/CUSTID,
] on session 88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.271 INFO - Got result: ERROR: Command execution failure. Please

search the user group at
https://groups.google.com/forum/#!forum/selenium-users for error details
from the log window. The error message is: can't access dead object on

session 88ffae4ba2df4c5eaa1a333b77ae6ee6
16:09:49.273 INFO - Command request: testComplete[, ] on session
88ffae4ba2df4c5eaa1a333b77ae6ee6

[sele...@googlecode.com]

Comment #23 on issue 4761 by bradj...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

I may have found a workaround for this bug; it's worked for me so far as
well as the reproduction steps in the original post. Hopefully it helps
others who, like me, were using an old version of FF.

In the latest IDE release (2.2.0), replace editor.js:707 with a try/catch
to handle the "dead object" error and set the lastWindow to null. (There
may be reasons for some of you to hang onto that old window object, but I
haven't experienced any problems so far.)

704 704 Editor.prototype.addCommand =
function(command,target,value,window,insertBeforeLastCommand) {
705 705 this.log.debug("addCommand: command=" + command + ", target="
+ target + ", value=" + value + " window.name=" + window.name);
706 706 if (this.lastWindow) {
707 - this.log.debug("window.name=" + window.name + ",
lastWindow.name=" + this.lastWindow.name);
707 + try {
708 + this.log.debug("window.name=" + window.name + ",
lastWindow.name=" + this.lastWindow.name);
709 + } catch (e) {
710 + this.lastWindow = null;
711 + this.log.debug("window.name=" + window.name);
712 + }
708 713 } else {
709 714 this.log.debug("window.name=" + window.name);
710 715 }

[sele...@googlecode.com]

Comment #24 on issue 4761 by rafalfu...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

any progress and a proper fix for it ?

[sele...@googlecode.com]

Comment #25 on issue 4761 by israel.o...@gmail.com: IDE/Core: can't access

dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

Where is the editor.js path?

[sele...@googlecode.com]

Comment #26 on issue 4761 by brad...@decipherinc.com: IDE/Core: can't

access dead object error
http://code.google.com/p/selenium/issues/detail?id=4761

Here is editor.js:
https://code.google.com/p/selenium/source/browse/ide/main/src/content/editor.js#707

Unpack the installed extension's XPI into the same extension directory,
remove any filename extension (so it's called something like "{...}"),
rename the original XPI file, modify the "{...}"/chrome/content/editor.js
file, and close Firefox, your changes will take effect when FF is reloaded.

[sele...@googlecode.com]

Updates:
Status: Fixed

Comment #27 on issue 4761 by Samit.Badle: IDE/Core: can't access dead
object error
http://code.google.com/p/selenium/issues/detail?id=4761

This issue was closed by revision 1d675b47e8bd.

[sele...@googlecode.com]

Comment #28 on issue 4761 by Samit.Badle: IDE/Core: can't access dead
object error
http://code.google.com/p/selenium/issues/detail?id=4761

Hi,

My commit fixes the Selenium IDE issue while recording tests as provided in
the steps to reproduce by David. The fix will be available in Selenium IDE
2.3.0 (next release).

This does not mean that there are no other dead object issues in Selenium
IDE or Selenium Core. The changes in Firefox would affect all interactions
with multiple windows or frames. Please raise a new issue to report them
with tests to reproduce.

Cheers,
Samit Badle
Selenium IDE Maintainer
Twitter: @samitbadle
Blog: http://blog.reallysimplethoughts.com/

[sele...@googlecode.com]

Comment #29 on issue 4761 by dlun...@gmail.com: IDE/Core: can't access dead
object error
http://code.google.com/p/selenium/issues/detail?id=4761

If you're willing to build your own copy of Firefox from the source, you
can comment out lines 907 and 908 of jswrapper.cpp...

These two:

e.removeFront();
NukeCrossCompartmentWrapper(cx, wobj);

That fixed all Dead Object errors for me. A pain I know. The Firefox people
should have left us some way to switch this on and off for automated
testing.