User:Rcampbell/LeakTests

15:17 < bz> OK
15:17 < bz> So the simplest way to get what it produces now, I think is:
15:17 < bz> touch bloat-cur.log
15:17 < bz> cp bloat-cur.log bloat-prev.log
15:17 < bz> env XPCOM_MEM_BLOAT_LOG=bloat-cur.log firefox -P default 
          resource:///res/bloatcycle.html
15:18 < bz> cat bloat-cur.log
15:18 < bz> perl mozilla/tools/tinderbox/bloatdiff.pl bloat-prev.log bloat-cur.log
15:18 < robcee> that's it?
15:18 < robcee> ah
15:19 < bz> and somewhere in there it needs to produce the actual Rlk number....
15:19 < bz> TinderboxPrint:<a title="refcnt Leaks" 
href="http://build-graphs.mozilla.org/graph/query.cgi?testname=refcnt_leaks&units=bytes&tbox=balsa-trunk&autoscale=1&days=7&avg=1&showpoint=2007:02:06:05:38:07,749664">RLk:732KB</a>
15:19 < robcee> let me try this on a command line to see if it works first
15:20 < bz> makes sense
15:21 < bz> so....
15:21 < bz> There's a tinderbox module for this
15:21 < bz> 
http://lxr.mozilla.org/mozilla/source/testing/tinderbox-standalone-tests/Tests/BloatTest.pm
15:21 < robcee> I don' tneed to invoke with --trace-malloc for this?
15:21 < robcee> yeah, it's probably fairly easy to setup with tinderbox
15:21 < bz> The thing doesn't
15:22 < bz> Well, all I'm saying is you could duplicate what that does.  ;)