570228 - sporadic 256-byte leak during mochitest-ipcplugins (leaking one instance each of nsDNSAsyncRequest, nsHTMLDNSPrefetch::nsListener, nsHostRecord, nsStringBuffer)

Status: RESOLVED WORKSFORME

(Core :: Networking, defect)

Description

[Daniel Holbert [:dholbert]]

Linux mozilla-central debug test mochitest-other on 2010/06/04 13:57:24
s: mv-moz2-linux-ix-slave03

{
nsTraceRefcntImpl::DumpStatistics: 881 entries
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 256 bytes during test execution
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of nsDNSAsyncRequest with size 48 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of nsHTMLDNSPrefetch::nsListener with size 12 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of nsHostRecord with size 64 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of nsHostResolver with size 124 bytes
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of nsStringBuffer with size 8 bytes
}
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1275685044.1275686217.16926.gz

Comment 1

[Benjamin Smedberg]

Why is this filed under plugins? Surely it's the DNS service that's leaking its own internal objects.

Comment 2

[Benjamin Smedberg]

This may be caused by the test at http://mxr.mozilla.org/mozilla-central/source/modules/plugin/test/mochitest/test_streamNotify.html?force=1#46 which seems like a perfectly valid thing for a test to do.

Comment 3

[Daniel Holbert [:dholbert]]

(In reply to comment #1)
> Why is this filed under plugins? Surely it's the DNS service that's leaking its
> own internal objects.

Because it was a problem during plugin tests, and we generally file orange-bugs in the component for the test(s) that are having problems.

But anyway, it sounds like you recommend moving to Networking (assuming that's the right component for DNS service issues).  Done.

Comment 4

[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