Closed Bug 463758 Opened 16 years ago Closed 7 years ago

Memory Leak during TopSite Run on http://www.alibaba.com

Categories

(Core :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: memory-leak)

Attachments

(1 file)

Attached file leak log
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.alibaba.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    12707 341876928      147 ( 6628.72 +/-   852.32) 497196736      171 ( 2689.32 +/-  3864.48)

nsTraceRefcntImpl::DumpStatistics: 857 entries
nsStringStats
 => mAllocCount:        7875208
 => mReallocCount:      1218647
 => mFreeCount:         7875155  --  LEAKED 53 !!!
 => mShareCount:        6976877
 => mAdoptCount:         723262
 => mAdoptFreeCount:     723259  --  LEAKED 3 !!!

http://www.alibaba.com: EXIT STATUS: NORMAL (3353.954185 seconds)
Flags: blocking1.9.1?
Small leak, not blocking.
Flags: blocking1.9.1? → blocking1.9.1-
No longer depends on: sisyphus-tracking
Filter on QUANTUMLEAK
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: