Closed
Bug 467394
Opened 16 years ago
Closed 16 years ago
Memory Leak during TopSite Run on http://www.51.com
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: cbook, Unassigned)
References
()
Details
(Keywords: memory-leak, regression)
Attachments
(1 file)
|
(deleted),
text/plain
|
Details |
Memory Leak during the automated Global 500 Testrun on http://www.51.com
Deep 0 Testsrun - 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 50 17019 271830 160 ( 833.14 +/- 811.45) 383157 286 ( 340.11 +/- 643.01)
nsTraceRefcntImpl::DumpStatistics: 674 entries
nsStringStats
=> mAllocCount: 9249
=> mReallocCount: 852
=> mFreeCount: 9202 -- LEAKED 47 !!!
=> mShareCount: 8717
=> mAdoptCount: 875
=> mAdoptFreeCount: 872 -- LEAKED 3 !!!
http://www.51.com: EXIT STATUS: NORMAL (31.384691 seconds)
Flags: blocking1.9.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
|
|
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
•