Closed
Bug 467011
Opened 16 years ago
Closed 15 years ago
Memory Leak during TopSite Run on http://www.lauxanh.us
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: cbook, Unassigned)
References
()
Details
(Keywords: memory-leak, regression)
Attachments
(1 file)
5.60 KB,
text/plain
|
Details |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20081125 Minefield/3.1b3pre ID:20081125210438 Memory Leak during the automated Global 500 Testrun on http://www.lauxanh.us 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 51 11443 202041 110 ( 618.69 +/- 750.31) 371566 157 ( 332.22 +/- 805.08) nsTraceRefcntImpl::DumpStatistics: 670 entries nsStringStats => mAllocCount: 11402 => mReallocCount: 1254 => mFreeCount: 11369 -- LEAKED 33 !!! => mShareCount: 9974 => mAdoptCount: 1259 => mAdoptFreeCount: 1256 -- LEAKED 3 !!! http://www.lauxanh.us: EXIT STATUS: NORMAL (30.428475 seconds)
Flags: blocking1.9.1?
Reporter | ||
Comment 1•15 years ago
|
||
not seen during the latest run, so i will mark this wfm for now
Status: NEW → RESOLVED
Closed: 15 years ago
Flags: blocking1.9.1?
Resolution: --- → WORKSFORME
Reporter | ||
Updated•15 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
•