This grew out of a newsgroup post and several other ideas. We need an extension for talos testing that will allow us to run specific scripted actions in the browser and measure the resulting memory footprint those actions cause. We could either re-use much of the peptest framework since it already solves much of the "driver" issue, or we could use marionette as our driver since it is a light weight shim into the browser. For reporting the memory, we're already modifying pageloader to properly report memory in bug 685632. This would also really help us make jlebar's request come true in bug 695702 as well. Honestly this is nearly a dupe of 695702. Here are the requirements from Nick: * Repeatability, historical comparisons * Run on-checkin * Able to be run by developers easily * auto-monitored by dev.tree-management and pulse (we sorta get that for free being a talos test) * results graphed at graphs-new.mozilla.org. * Memory overhead of the extension is not an issue, but at the same time, the extension must not inflict any memory leaks in the browser. The overhead should be consistent so that it doesn't introduce randomness in our numbers. * Should measure "resident" (a.k.a RSS) and "explicit" from about:memory would be a good start, for desktop. see bug 685632 * For any E10S build (XUL android, desktop firefox etc) then we should measure RSS if the chrome and content processes are listed separately, PSS if we sum them. Again see Bug 685632 for discussion about this.

> This would also really help us make jlebar's request come true in bug 695702 > as well. Honestly this is nearly a dupe of 695702. That should be bug 695072.