Closed Bug 468172 Opened 16 years ago Closed 16 years ago

Memory Leak during TopSite Run on http://www.origo.hu

Categories

(Core :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: memory-leak, regression)

Attachments

(1 file, 1 obsolete file)

Attached file test/leak log (obsolete) (deleted) —
Memory Leak during the automated Global 500 Testrun on http://www.origo.hu Deep 0 Testsrun and latest 1.9.1 Mozilla-Central Debug Build Build id :20081204204348 on Mac 10.5- so Frontpage only Requesting blocking 1.9.1 because its a Website from the Global 500 List. Also i have not seen this leaks on Testruns before, so this is maybe a regression. 0 TOTAL 26 14007 703069 412 ( 2377.13 +/- 1972.51) 927857 420 ( 982.43 +/- 1751.29) nsTraceRefcntImpl::DumpStatistics: 712 entries nsStringStats => mAllocCount: 23747 => mReallocCount: 2465 => mFreeCount: 23559 -- LEAKED 188 !!! => mShareCount: 17821 => mAdoptCount: 2316 => mAdoptFreeCount: 2313 -- LEAKED 3 !!! http://www.origo.hu: EXIT STATUS: NORMAL (10.939437 seconds)
Flags: blocking1.9.1?
I don't see any leak stats in that log?
Attached file leak/test log (deleted) —
oh snap, sorry wrong file (its the stack for the assertion i saw on this site :) Here is the correct Test/Leak Log
Attachment #351624 - Attachment is obsolete: true
not seen during the latest run, so i will mark this wfm for now
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: blocking1.9.1?
Resolution: --- → WORKSFORME
Likely fixed (at least in part) by bug 473845.
No longer depends on: sisyphus-tracking
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: