Closed Bug 658745 Opened 14 years ago Closed 12 years ago

Intermittent browser-chrome leak of 1 nsCacheEntry and 1 nsStringBuffer

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

Calling this front-end rather than netwerk because bz took a peek at the log, and was flabbergasted by how something browserly was hanging onto things so we would up with 500-odd domwindows to get rid of at shutdown, including apparently the one that was still desperately clinging to this nsCacheEntry http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1305941364.1305945463.28696.gz&fulltext=1 Rev3 WINNT 5.1 mozilla-central debug test mochitest-other on 2011/05/20 18:29:24 s: talos-r3-xp-013 (toward the start of the shutdown spew) --DOCSHELL 07CFEBF8 == 11 --DOCSHELL 033C9D10 == 10 WARNING: DeactivateEntry: unable to bind active entry : file e:/builds/moz2_slave/cen-w32-dbg/build/netwerk/cache/nsCacheService.cpp, line 2264 --DOCSHELL 03C361F0 == 9 --DOCSHELL 19B5F098 == 8 --DOCSHELL 037D8B90 == 7 --DOCSHELL 23833698 == 6 --DOCSHELL 235F9388 == 5 --DOCSHELL 2277BD40 == 4 --DOCSHELL 2316C4E0 == 3 --DOCSHELL 23720630 == 2 --DOMWINDOW == 528 (18121E78) [serial = 5997] [outer = 2143C460] [url = about:blank] ... TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 104 bytes during test execution TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of nsCacheEntry with size 96 bytes TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | leaked 1 instance of nsStringBuffer with size 8 bytes
Most if not all of the mailnews xpcshell tests are leaking a single nsStringBuffer, and if I'm interpreting nsStringStats correctly, the nsStringBuffer has no allocated data (stringstats claims we're allocating and freeing the same number of bytes).
the mailnews leakage most likely has to do with a static nsCString
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: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.