691165 - mochitest-other leaks AtomImpl / BackstagePass / BodyRule / Connection

Status: RESOLVED WORKSFORME

Description

[Richard Newman [:rnewman]]

Happened twice on services-central in succession.

nsTraceRefcntImpl::DumpStatistics: 1283 entries
TEST-PASS | automationutils.processLeakLog() | no leaks detected!
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 4133955 bytes during test execution
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 509 instances of AtomImpl with size 40 bytes each (20360 bytes total)
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of BackstagePass with size 48 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 14 instances of BodyRule with size 32 bytes each (448 bytes total)
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 2 instances of Connection with size 200 bytes each (400 bytes total)
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of DR_State with size 48 bytes

Sorry for doubtless filing this wrong, and in the wrong component!

Comment 1

[Richard Newman [:rnewman]]

https://tbpl.mozilla.org/php/getParsedLog.php?id=6641426&tree=Services-Central

and 

https://tbpl.mozilla.org/php/getParsedLog.php?id=6644576&tree=Services-Central

Comment 2

[Philipp von Weitershausen [:philikon]]

Happening on Win and OSX too, e.g.:

https://tbpl.mozilla.org/php/getParsedLog.php?id=6663395&tree=Services-Central
https://tbpl.mozilla.org/php/getParsedLog.php?id=6636225&tree=Services-Central
https://tbpl.mozilla.org/php/getParsedLog.php?id=6618551&tree=Services-Central
https://tbpl.mozilla.org/php/getParsedLog.php?id=6583626&tree=Services-Central
https://tbpl.mozilla.org/php/getParsedLog.php?id=6576963&tree=Services-Central

Comment 3

[Ed Morley [:emorley]]

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