Updates:
Summary: Selenium failures from webkit change 45797.
Status: Assigned
Owner: [email protected]
Cc: [email protected] [email protected]
Labels: -Pri-2 Pri-1
Comment #2 on issue 16691 by [email protected]: Selenium failures from
webkit change 45797.
http://code.google.com/p/chromium/issues/detail?id=16691
The regression is caused by WebKit change
http://trac.webkit.org/changeset/45797
2009-07-13 Mads Ager < [email protected]>
Fix memory leak in the V8 binding layer.
https://bugs.webkit.org/show_bug.cgi?id=27163
Reverting changes in V8Proxy.cpp fixes selenium tests. The failing test
opens a popup window and then re-
navigates that popup using window.location.href=<new_location>. It also
watches for the location.href to
change and fails when it does not change to the new one after a timeout.
The actual navigation happens, likely
the way selenium 'watches' the location is broken, I didn't debug this to
the end.
The way to run selenium tests:
1. make sure in your .gclient file the line "src/data/selenium_core": None
is not present (comment it out)
2. run Chrome, load src\data\selenium_core\Index.html, click "Selenium
TestSuite" link
3. select and run TestFramesSpecialTargets. Normally, it runs to the end,
with this bug it hangs.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
