Changes

The new-style (nsTraceMalloc-based) leak stats are displayed in the bottom-right panel after clicking on a debug build's "B" and look like this:

<table style="marginul><li>s: 1em auto" border="1" width="120" linux-ix-slave35</li><trli><td style[http://graphs.mozilla.org/graph.html#tests="background: &#91;&#1d191; text-align: center28,1,6&#93; font: medium monospace&#93; paddingLk: 2em 1em"702KB]</li><span styleli> [http://graphs.mozilla.org/graph.html#tests="text-decoration:underline&#91;&#91;29,1,6&#93; color: &#00e93; cursorMH:pointer">L32.0MB]</spanli> <span styleli> [http://graphs.mozilla.org/graph.html#tests="text-decoration:underline&#91;&#91;30,1,6&#93; color: &#00e93; cursorA:pointer">C498010]</spanli><brli>Lkcheck:382KB<br>MH:7.75MB<br>A:391K<31015/td>0</trli></tableul>

These statistics are generated using trace-malloc. They therefore give accurate aggregate statistics for all heap allocations during the test. Like the old-style leak statistics, the action tested is loading of a browser window and a run through the bloat URLs (bloaturls.txt). The Lk (leak) number is the total number of bytes (not counting any overhead in the allocator) allocated on the heap and not freed over the entire run. This number (as does the number in the old-style leak statistics) includes shutdown leaks, leaks that happen only once for a run of the browser, but there are more here since most shutdown leaks are not of objects logged by nsTraceRefcnt. The MH (max heap, or a meaningful bloat number that I gave a name other than "bloat") is the number of bytes allocated on the heap at the point during the run when the heap was at its maximum size (again, excluding overhead). The A (allocations) number is the total number of allocations over the run, and is an indicator of a subset of performance rather than an indicator of memory use, although high allocation churn could contribute to fragmentation.