Closed
Bug 463757
Opened 16 years ago
Closed 14 years ago
Memory Leak during TopSite Run on http://www.shopping.com
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: cbook, Unassigned)
References
()
Details
(Keywords: memory-leak, Whiteboard: [nsDocument leak (1)])
Attachments
(1 file)
35.07 KB,
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.shopping.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 41 536148 79210162 10299 ( 4331.71 +/- 4625.00) 113304148 6229 ( 2638.30 +/- 3709.24) nsTraceRefcntImpl::DumpStatistics: 833 entries nsStringStats => mAllocCount: 2331194 => mReallocCount: 391668 => mFreeCount: 2329015 -- LEAKED 2179 !!! => mShareCount: 2060830 => mAdoptCount: 186962 => mAdoptFreeCount: 186959 -- LEAKED 3 !!! http://www.shopping.com: EXIT STATUS: NORMAL (1318.206191 seconds)
Flags: blocking1.9.1?
Updated•16 years ago
|
Whiteboard: [nsDocument leak (1)]
Comment 1•16 years ago
|
||
Hopefully covered by other blocking leak bugs, not blocking on this one.
Depends on: 458401
Flags: blocking1.9.1? → blocking1.9.1-
Reporter | ||
Updated•15 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
•