Closed Bug 835198 Opened 8 years ago Closed 8 years ago

Intermittent browser_bug676619.js | Test timed out, found a tab and a window, leaked until shutdown, and a leak

Categories

(Core :: DOM: Core & HTML, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=19175936&tree=Firefox
Rev4 MacOSX Snow Leopard 10.6 mozilla-central debug test mochitest-browser-chrome on 2013-01-26 19:11:50 PST for push 47684913d63d
slave: talos-r4-snow-079

TEST-INFO | chrome://mochitests/content/browser/browser/base/content/test/browser_bug676619.js | window opened, waiting for focus
TEST-INFO | chrome://mochitests/content/browser/browser/base/content/test/browser_bug676619.js | must wait for load
TEST-INFO | chrome://mochitests/content/browser/browser/base/content/test/browser_bug676619.js | must wait for focus
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/browser_bug676619.js | Test timed out
(screenshot of a data URI claiming to be "Connecting...")
INFO TEST-END | chrome://mochitests/content/browser/browser/base/content/test/browser_bug676619.js | finished in 30135ms
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/browser_bug676619.js | Found a tab after previous test timed out: http://mochi.test:8888/browser/browser/base/content/test/download_page.html
WARNING: NS_ENSURE_TRUE(mMutable) failed: file ../../../../netwerk/base/src/nsSimpleURI.cpp, line 265
TEST-INFO | checking window state
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/browser_bug676619.js | Found a unknown window after previous test timed out
...
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/browser_bug676619.js | leaked until shutdown [nsGlobalWindow #755 about:blank]
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/browser_bug676619.js | leaked until shutdown [nsGlobalWindow #754 about:blank]
...
nsTraceRefcntImpl::DumpStatistics: 1470 entries
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 681707 bytes during test execution
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 207 instances of AtomImpl with size 40 bytes each (8280 bytes total)
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of BackstagePass with size 48 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 12 instances of DOMCSSDeclarationImpl with size 32 bytes each (384 bytes total)
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 12 instances of DOMCSSStyleRule with size 56 bytes each (672 bytes total)
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of DR_State with size 48 bytes
TEST-INFO | automationutils.processLeakLog() | leaked 2 instances of DocumentRule with size 72 bytes each (144 bytes total)
TEST-INFO | automationutils.processLeakLog() | leaked 4 instances of ExpirationTrackerObserver with size 32 bytes each (128 bytes total)
TEST-INFO | automationutils.processLeakLog() | leaked 3 instances of FragmentOrElement with size 112 bytes each (336 bytes total)
TEST-INFO | automationutils.processLeakLog() | leaked 2 instances of GLContext with size 1688 bytes each (3376 bytes total)
TEST-INFO | automationutils.processLeakLog() | leaked 2 instances of GenericFactory with size 32 bytes each (64 bytes total)
TEST-INFO | automationutils.processLeakLog() | leaked 7 instances of GroupRule with size 56 bytes each (392 bytes total)
TEST-INFO | automationutils.processLeakLog() | leaked 1 instance of HTMLBodyElement with size 136 bytes
etc.
I didn't really notice this until today. Maybe I could get a screenshot? I assume that for some reason at least one download window doesn't appear.
You can indeed get a screenshot - "test timed out" means that immediately after that, there'll be a data: URI of a screenshot in the log. The one I just looked at, from comment 35, is spectacularly unhelpful, three blank tabs with the middle one selected, but it's possible there are more useful ones in one of the other logs.
Heh, the other thing you're likely to notice when you expand the tbplbot comments to get at more log links, is that there was one instance of this, or more or less this, on a Win8 slave in comment 20, and that instance was precisely at 03:00 when they start doing scheduled maintenance (on which there is a releng bug, because it does just that, causes intermittent failures that intermittently happen at 03:00), and *every* other instance was on talos-r4-snow-079.

Move along, people, nothing to see here except a badslave.
Depends on: t-snow-r4-0077
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.