Closed
Bug 463761
Opened 16 years ago
Closed 14 years ago
Memory Leak during TopSite Run on http://www.blogchina.com
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: cbook, Unassigned)
References
()
Details
(Keywords: memory-leak)
Attachments
(1 file)
|
(deleted),
text/plain
|
Details |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b2pre) Gecko/20081102 Minefield/3.1b2pre
Memory Leak during the automated Global 500 Testrun on http://www.blogchina.com
Requesting blocking 1.9.1 because its a Website from the Global 500 List. I will run another test for 1.9.0 Builds to check if this is a regression in 1.9.1
0 TOTAL 39 16267 836740 127 ( 5962.16 +/- 6251.63) 1004427 246 ( 2146.66 +/- 3312.54)
nsTraceRefcntImpl::DumpStatistics: 657 entries
nsStringStats
=> mAllocCount: 20402
=> mReallocCount: 2147
=> mFreeCount: 20366 -- LEAKED 36 !!!
=> mShareCount: 22626
=> mAdoptCount: 3105
=> mAdoptFreeCount: 3102 -- LEAKED 3 !!!
http://www.blogchina.com: EXIT STATUS: NORMAL (127.162460 seconds)
Flags: blocking1.9.1?
|
Reporter | |
Updated•16 years ago
|
Blocks: sisyphus-tracking
No longer depends on: sisyphus-tracking
WFM on trunk
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•