>TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 24 bytes during test execution >TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 3 instances of BrowserNPObject with size 8 bytes each (24 bytes total) [...] >TinderboxPrint: jsreftest<br/>53963/0/908&nbsp;<em class="testfail">LEAK</em> http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1261166668.1261175970.7265.gz WINNT 5.2 mozilla-central debug test everythingelse on 2009/12/18 12:04:28 s: win32-slave42

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1262000403.1262007401.32302.gz WINNT 5.2 mozilla-central debug test everythingelse on 2009/12/28 03:40:03

Comment 2 is a failure in the "test_empty_search.js" xpcshell test, with no leak -- not this bug. (I don't think there's any bug filed on that particular failure, at the moment)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1262757429.1262764734.26019.gz WINNT 5.2 mozilla-central debug test everythingelse on 2010/01/05 21:57:09 s: win32-slave30 { TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 56 bytes during test execution TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 7 instances of BrowserNPObject with size 8 bytes each (56 bytes total) } Looks like this leak has increased recently, to 7 instances (up from the original 3).

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1263956071.1263957664.30987.gz WINNT 5.2 mozilla-central debug test jsreftest on 2010/01/19 18:54:31 s: win32-slave25

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1264155980.1264157664.892.gz WINNT 5.2 mozilla-central debug test jsreftest on 2010/01/22 02:26:20 s: win32-slave25

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