Performance:Leak Tools: Difference between revisions

m (Reverted edits by IsabellaArnold (talk) to last revision by Jlebar)
Line 124: Line 124:
   garbageCollect(Components.classes["@mozilla.org/cycle-collector-logger;1"]
   garbageCollect(Components.classes["@mozilla.org/cycle-collector-logger;1"]
     .createInstance(Components.interfaces.nsICycleCollectorListener))
     .createInstance(Components.interfaces.nsICycleCollectorListener))
Nightly builds before 2012 defaulted to all traces, newer builds logs the
same edges what cycle collector normally uses.
A new method allTraces() was added so the the old behavior can be achieved when
needed:
window.QueryInterface(Components.interfaces.nsIInterfaceRequestor).
  getInterface(Components.interfaces.nsIDOMWindowUtils).
  garbageCollect(Components.classes["@mozilla.org/cycle-collector-logger;1"]
    .createInstance(Components.interfaces.nsICycleCollectorListener).allTraces())


A file cc-edges-NNNN.log will be created in Firefox's current working directory (usually the current working directory where Firefox was started). This file contains a dump of the heap known to the cycle collector, which includes JS objects and also native C++ objects that participate in cycle collection.
A file cc-edges-NNNN.log will be created in Firefox's current working directory (usually the current working directory where Firefox was started). This file contains a dump of the heap known to the cycle collector, which includes JS objects and also native C++ objects that participate in cycle collection.
Confirmed users
157

edits