Open
Bug 989362
Opened 10 years ago
Updated 2 years ago
GC between tests causes document.tooltipNode to be null causing an exception in tabbrowser.xml::createTooltip
Categories
(Firefox :: Tabbed Browser, defect)
Firefox
Tabbed Browser
Tracking
()
NEW
People
(Reporter: miker, Unassigned)
References
Details
Attachments
(1 file)
960 bytes,
patch
|
Details | Diff | Splinter Review |
We added the following between each mochitest-bc to stop GC timing out tests: SpecialPowers.DOMWindowUtils.garbageCollect(); Strangely, browser/base/content/tabbrowser.xml then fails in createTooltip because document.tooltipNode is sometimes null / undefined in non-debug builds. We don't see why GC should affect this. The patch that causes and works around the problem: https://bug983948.bugzilla.mozilla.org/attachment.cgi?id=8398521 Also see the orange bcs in this try push: https://tbpl.mozilla.org/?tree=Try&rev=de5d5a0fc07a
Comment 1•10 years ago
|
||
(See bug 983948 comment 96)
Comment 2•10 years ago
|
||
As a guess, test browser_bug585558.js is testing hovering over the tabs, which will trigger a tooltip to appear after 500ms. Then the tab is closed, which will make the triggering node invalid. I didn't test this patch or theory though.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•