Closed Bug 463702 Opened 16 years ago Closed 14 years ago

Memory Leak during TopSite Test on http://www.dvd4arab.com

Categories

(Core :: General, defect, P2)

x86
macOS
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: memory-leak, regression, Whiteboard: [nsGlobalWindow leak (8)])

Attachments

(1 file)

Attached file leak log
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b2pre) Gecko/20081106 Firefox/3.1b2pre


Found during the automated Global 500 TopSite Run on http://www.dvd4arab.com

Have not seen this Leak before, so adding regression keyword and blocking flag.

   0 TOTAL                                          22  1264412  3594061    41261 ( 7656.73 +/-  5786.66)  8393257    35973 ( 2261.68 +/-  3740.04)

nsTraceRefcntImpl::DumpStatistics: 726 entries
nsStringStats
 => mAllocCount:          60266
 => mReallocCount:        11003
 => mFreeCount:           57205  --  LEAKED 3061 !!!
 => mShareCount:          55334
 => mAdoptCount:           5032
 => mAdoptFreeCount:       5029  --  LEAKED 3 !!!

http://www.dvd4arab.com: EXIT STATUS: NORMAL (1073.231760 seconds)
Flags: blocking1.9.1?
Whiteboard: [nsGlobalWindow leak (8)]
Assignee: nobody → bent.mozilla
Flags: blocking1.9.1? → blocking1.9.1+
Priority: -- → P2
Can't reproduce any leaks here... Maybe peterv fixed it, or maybe i haven't hit the magic link? Tomcat, can you retest and renominate if you leak again? I'm using a debug build from 20081208.
Flags: blocking1.9.1+
Assignee: bent.mozilla → nobody
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: