Closed Bug 461384 Opened 16 years ago Closed 7 years ago

Memory leak during the Start of the TopSite Test

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: cbook, Unassigned)

References

Details

(Keywords: memory-leak) 

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b2pre) Gecko/20081018 Firefox/3.1b2pre

This Leak happened on 1.9.1 while restarting Firefox after the Spider Extension was installed, to run the TopSite Testrun

Might be the same Problem as Bug 415991. Will retest after Bug 415991 is fixed.

== BloatView: ALL (cumulative) LEAK STATISTICS

     |<----------------Class--------------->|<-----Bytes------>|<----------------Objects---------------->|<--------------References-------------->|
                                              Per-Inst   Leaked    Total      Rem      Mean       StdDev     Total      Rem      Mean       StdDev
   0 TOTAL                                          29       76   144070        2 (  566.29 +/-   822.35)   396378        2 (  449.45 +/-   795.25)
 121 nsBaseAppShell                                 64       64        1        1 (    1.00 +/-     0.00)     1693        1 (    8.05 +/-     1.36)
 474 nsRunnable                                     12       12      538        1 (  124.64 +/-   113.88)     1658        1 (  121.84 +/-   113.86)

nsTraceRefcntImpl::DumpStatistics: 656 entries
nsStringStats
 => mAllocCount:          10843
 => mReallocCount:          694
 => mFreeCount:           10843
 => mShareCount:           7168
 => mAdoptCount:           1057
 => mAdoptFreeCount:       1057

Start Spider: try 1: EXIT STATUS: NORMAL (5.418906 seconds)
Blocks: sisyphus-tracking
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.