Closed Bug 463752 Opened 16 years ago Closed 14 years ago

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

Categories

(Core :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: memory-leak)

Attachments

(1 file)

Attached file leak log (deleted) —
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.pornotube.com

Requesting blocking 1.9.1 because its a Website from the Global 500 List. I will run another automated test for 1.9.0 Builds to check if this is a regression in 1.9.1

 0 TOTAL                                          49     7947   295055       77 (  789.71 +/-   827.80)   453578       78 (  375.74 +/-   813.72)

nsTraceRefcntImpl::DumpStatistics: 677 entries
nsStringStats
 => mAllocCount:          12160
 => mReallocCount:         1310
 => mFreeCount:           12137  --  LEAKED 23 !!!
 => mShareCount:          10709
 => mAdoptCount:           1712
 => mAdoptFreeCount:       1709  --  LEAKED 3 !!!

http://www.pornotube.com: EXIT STATUS: NORMAL (13.460166 seconds)
Flags: blocking1.9.1?
Small leak, not blocking.
Flags: blocking1.9.1? → blocking1.9.1-
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.

Attachment

General

Created:
Updated:
Size: