Closed
Bug 467782
Opened 16 years ago
Closed 16 years ago
Memory Leak during TopSite Run on http://www.gamespot.com
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: cbook, Unassigned)
References
()
Details
(Keywords: memory-leak, regression, Whiteboard: [nsDocShell leak (1)])
Attachments
(1 file)
|
(deleted),
text/plain
|
Details |
Memory Leak during the automated Global 500 Testrun on http://www.gamespot.com
Deep 0 Testsrun and latest 1.9.1 Mozilla-Central Debug Build - so Frontpage only
Requesting blocking 1.9.1 because its a Website from the Global 500 List.
Also i have not seen this leaks on Testruns before, so this is maybe a
regression.
0 TOTAL 29 255364 855456 8120 ( 3524.46 +/- 3623.49) 1243991 4337 ( 2054.11 +/- 3464.62)
nsTraceRefcntImpl::DumpStatistics: 709 entries
nsStringStats
=> mAllocCount: 30524
=> mReallocCount: 2860
=> mFreeCount: 29321 -- LEAKED 1203 !!!
=> mShareCount: 27714
=> mAdoptCount: 3763
=> mAdoptFreeCount: 3760 -- LEAKED 3 !!!
http://www.gamespot.com: EXIT STATUS: NORMAL (15.772634 seconds)
Flags: blocking1.9.1?
|
||
Updated•16 years ago
|
Whiteboard: [nsDocShell leak (1)]
|
Reporter | |
Comment 1•16 years ago
|
||
not seen during the latest run, so i will mark this wfm for now
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: blocking1.9.1?
Resolution: --- → WORKSFORME
|
||
Comment 2•16 years ago
|
||
Likely fixed (at least in part) by bug 473845.
|
|
Reporter | |
Updated•16 years ago
|
Blocks: sisyphus-tracking
No longer depends on: sisyphus-tracking
You need to log in
before you can comment on or make changes to this bug.
Description
•