Closed
Bug 461383
Opened 16 years ago
Closed 7 years ago
Memory leak during TopSite Test on http://www.onet.pl
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: cbook, Unassigned)
References
()
Details
(Keywords: memory-leak, regression, Whiteboard: [nsDocShell leak (1)])
Attachments
(1 file)
|
(deleted),
text/plain
|
Details |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b2pre) Gecko/20081018 Firefox/3.1b2pre Found during the automated Global-500 Topsite Test on http://www.onet.pl I have not seen this on the 1.9.0 Testrun, so adding the regression and blocking keyword nsTraceRefcntImpl::DumpStatistics: 803 entries nsStringStats => mAllocCount: 2749336 => mReallocCount: 633247 => mFreeCount: 2747322 -- LEAKED 2014 !!! => mShareCount: 2722445 => mAdoptCount: 311403 => mAdoptFreeCount: 311400 -- LEAKED 3 !!! http://www.onet.pl: EXIT STATUS: NORMAL (2661.075998 seconds)
Flags: blocking1.9.1?
|
||
Updated•16 years ago
|
Whiteboard: [nsDocShell leak (1)]
|
|
||
Comment 1•16 years ago
|
||
Hopefully covered by other blocking leak bugs, not blocking on this one.
Depends on: 463093
Flags: blocking1.9.1? → blocking1.9.1-
|
Reporter | |
Updated•16 years ago
|
Blocks: sisyphus-tracking
No longer depends on: sisyphus-tracking
|
||
Comment 2•7 years ago
|
||
Filter on QUANTUMLEAK
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•