Closed
Bug 463760
Opened 17 years ago
Closed 8 years ago
Memory Leak during TopSite Run on http://www.hurriyet.com.tr
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: cbook, Unassigned)
References
()
Details
(Keywords: memory-leak, Whiteboard: [nsDocument leak (1)])
Attachments
(1 file)
|
34.77 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.hurriyet.com.tr
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
Total Rem Mean StdDev
0 TOTAL 39 517660 92459633 10060 ( 3725.00 +/- 3181.16) 101755742 5922 ( 2260.06 +/- 3205.28)
nsTraceRefcntImpl::DumpStatistics: 756 entries
nsStringStats
=> mAllocCount: 1541724
=> mReallocCount: 323035
=> mFreeCount: 1539534 -- LEAKED 2190 !!!
=> mShareCount: 1473213
=> mAdoptCount: 178629
=> mAdoptFreeCount: 178626 -- LEAKED 3 !!!
http://www.hurriyet.com.tr: EXIT STATUS: NORMAL (1020.988184 seconds)
Flags: blocking1.9.1?
|
||
Updated•17 years ago
|
Whiteboard: [nsDocument leak (1)]
|
|
||
Comment 1•17 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•16 years ago
|
Blocks: sisyphus-tracking
No longer depends on: sisyphus-tracking
|
||
Comment 2•8 years ago
|
||
Filter on QUANTUMLEAK
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•