Closed Bug 463093 Opened 16 years ago Closed 7 years ago

Memory leak during TopSite Test on http://www.hp.com

Categories

(Core :: General, defect, P2)

x86
Windows XP
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: memory-leak, regression, Whiteboard: [nsDocShell leak (1)])

Attachments

(1 file)

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2pre) Gecko/20081030 Minefield/3.1b2pre

Found during the automated Global 500 Memory Testrun on http://www.hp.com
I have not seen this Leak on the 1.9.0 Testrun, so adding the regression keyword.

 0 TOTAL                                          26    14819 30098312      377 ( 4844.26 +/-  3952.26) 39357422      421 ( 1989.13 +/-  2762.84)

nsTraceRefcntImpl::DumpStatistics: 729 entries
nsStringStats
 => mAllocCount:         519294
 => mReallocCount:        91805
 => mFreeCount:          519129  --  LEAKED 165 !!!
 => mShareCount:         577548
 => mAdoptCount:          71877
 => mAdoptFreeCount:      71874  --  LEAKED 3 !!!

http://www.hp.com: EXIT STATUS: NORMAL (928.844000 seconds)
Flags: blocking1.9.1?
Whiteboard: [nsDocShell leak (1)]
Assignee: nobody → bent.mozilla
Flags: blocking1.9.1? → blocking1.9.1+
Priority: -- → P2
Blocks: 461383
Blocks: 463092
Can't reproduce any leaks here... Tried the front page and a few of the links. Please renominate if you can reproduce?
Assignee: bent.mozilla → nobody
Flags: 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: