Closed Bug 463759 Opened 16 years ago Closed 7 years ago

Memory Leak during TopSite Run on http://www.xtube.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.xtube.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                                          36     7947  6166362       78 ( 5468.54 +/-  4116.32)  7395603       76 ( 2783.74 +/-  4070.83)

nsTraceRefcntImpl::DumpStatistics: 699 entries
nsStringStats
 => mAllocCount:         112945
 => mReallocCount:        23446
 => mFreeCount:          112921  --  LEAKED 24 !!!
 => mShareCount:         128793
 => mAdoptCount:          22516
 => mAdoptFreeCount:      22513  --  LEAKED 3 !!!

http://www.xtube.com: EXIT STATUS: NORMAL (118.178024 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: