Closed Bug 598294 Opened 10 years ago Closed 8 years ago

Intermittent failure in browser_tab_dragdrop2.js | Test timed out & Found a browser window after previous test timed out

Categories

(Firefox :: Tabbed Browser, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: dao, Unassigned)

References

Details

(Keywords: intermittent-failure)

No description provided.
Blocks: 438871
Whiteboard: [orange]
Duplicate of this bug: 598327
Duplicate of this bug: 597782
From bug 598327 comment 0:

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1285062940.1285065146.11271.gz
Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central debug test mochitest-other on
2010/09/21 02:55:40

Interesting in the log:

JavaScript error:
chrome://mochikit/content/browser/browser/base/content/test/browser_tab_dragdrop2.js,
line 36: window_C.gBrowser.getBrowserForTab(window_C.gBrowser.tabs[0]).docShell
is null


JavaScript error: chrome://browser/content/tabbrowser.xml, line 1667:
aOtherTab.ownerDocument.defaultView is null
Version: unspecified → Trunk
See bug 760424, this test seems to have a similar issue:

http://mxr.mozilla.org/mozilla-central/source/browser/base/content/test/browser_tab_dragdrop2.js?rev=574b0fb35604#21

The "load" event listener is added on window_B.gBrowser, but removed on window_B.
Component: Document Navigation → Tabbed Browser
Product: Core → Firefox
QA Contact: docshell → tabbed.browser
Though I guess we haven't actually seen this failure in a long time...
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.