Closed Bug 666710 Opened 8 years ago Closed 7 years ago

Sporadic "leaked 52930 (or 27978) bytes during test execution", leaking a BackstagePass, Connection, HttpBaseChannel, QuotaCallback, and 10 Mutex (with 3 fxfeeds.mozilla.com URLs leaked)

Categories

(Core :: General, defect)

defect
Not set

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: dholbert, Unassigned)

References

()

Details

(Keywords: intermittent-failure, memory-leak)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1308849342.1308853307.30349.gz
Rev3 MacOSX Snow Leopard 10.6.2 mozilla-central debug test mochitests-2/5 on 2011/06/23 10:15:42
s: talos-r3-snow-030
{
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 52930 bytes during test execution
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of BackstagePass with size 48 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of Connection with size 200 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of HttpBaseChannel with size 672 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 10 instances of Mutex with size 24 bytes each (240 bytes total)
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of QuotaCallback with size 24 bytes
}
Version: 1.9.2 Branch → Trunk
TBPL's "analyze the leak" link says that no dom windows were leaked, btw.
Component: Networking → General
QA Contact: networking → general
Whiteboard: [orange]
Just hit this on WinXP Debug, too:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1308866829.1308871065.8762.gz
Rev3 WINNT 5.1 mozilla-central debug test mochitests-2/5 on 2011/06/23 15:07:09
s: talos-r3-xp-023
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 27978 bytes during test execution
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of BackstagePass with size 24 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of Connection with size 112 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of HttpBaseChannel with size 344 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 10 instances of Mutex with size 12 bytes each (120 bytes total)
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of QuotaCallback with size 12 bytes
OS: Mac OS X → All
Hardware: x86_64 → All
Summary: Sporadic "leaked 52930 bytes during test execution", leaking a BackstagePass, Connection, HttpBaseChannel, QuotaCallback, and 10 Mutex → Sporadic "leaked 52930 (or 27978) bytes during test execution", leaking a BackstagePass, Connection, HttpBaseChannel, QuotaCallback, and 10 Mutex
Indeed! Those same URLs were leaked in the log from comment 0.
Summary: Sporadic "leaked 52930 (or 27978) bytes during test execution", leaking a BackstagePass, Connection, HttpBaseChannel, QuotaCallback, and 10 Mutex → Sporadic "leaked 52930 (or 27978) bytes during test execution", leaking a BackstagePass, Connection, HttpBaseChannel, QuotaCallback, and 10 Mutex (with 3 fxfeeds.mozilla.com URLs leaked)
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.