an instrumented copy of membuster lives here:
These stats show that m-c is carrying 50-100 DOMWindows more than 3.6, and m-c leaves 200 DOMWindows around after the run has completed. The detailed m-c stats show that image-data, mjit code, and layout (to a lesser extent) are the bigger bits. js/gc-heap doesn't shrink.
Unfortunately, these stats don't yet account for the full browser's memory usage. The builds are debug anyway. I want to add total counts of JSObjects, and the size of the Cycle Collector graph.
This page is run with these prefs:
and people.mozilla.com is allowed to open popups.
I should add, I also keep an altered copy of about:memory open during the run. It runs in a 10 second setTimeout, so I can track the stats over time.
Created attachment 509931 [details] [diff] [review]
my printfs for logging
the WIP python analysis scripts. it processes the stdout/stderr of a debug browser build running membuster (or anything, I guess) and makes graphs.
Unfortunately the URLs in comment 0 no longer work because Sayre's page is gone. The python scripts in comment 3 are still available.
Seems to be self-contained. Could probably be attached to the bug.
This bug isn't useful any more.