When a leak is detected, the extension presents the user (or application/extension developer!) with a dialog with information about the leaked objects. (The alerts can also be triggered by bugs in the core code. See the [http://dbaron.org/mozilla/leak-monitor/ extension's homepage] for more details.)
==== JavaScript heap dump ====
Setting the <code>XPC_SHUTDOWN_HEAP_DUMP</code> environment variable to a file name will cause XPConnect to, at shutdown, dump a log to that file explaining why all remaining JS objects are still alive. This may be sufficient to debug some JS-related leaks without the full rebuild required by DEBUG_CC. It also shows more information about reachability, since it shows property names for all connections.
==== Cycle collector and JavaScript heap dump ====