The process for getting about:memory dumps off your device has changed a bit.
To get the new script, update your B2G repository (git pull, not repo sync). The major changes are: 1) The script is now in the tools/ directory. 2) You don't need to gunzip anything anymore. Instead, the script will try to open about:memory for the memory report after it downloads it from the device. The process for getting memory dumps off a desktop b2g build is unchanged. (See quoted message below for instructions.) I hope to streamline this soon. Please don't forget to git pull regularly so you get any future updates to this and other scripts. Regards, -Justin On Fri, Oct 12, 2012 at 6:06 PM, Justin Lebar <[email protected]> wrote: > I've been receiving a lot of questions about how to do this, so I > wanted to send the instructions to a wider audience. > > If you want to get memory reports off a device (so you can view the > contents of the device's about:memory), do the following: > > * Update your b2g repository. (That is, git fetch/pull -- repo sync > is not sufficient.) > * Run get-about-memory.py. > * $ cd about-memory-XXX && gunzip merged-reports.gz > * Load a recent Firefox nightly build on your desktop. > * Navigate to about:memory > * Scroll to the bottom, click "read reports from file", and select the > merged-reports file in the directory created by the script. > > See ./get-about-memory.py --help for other tricks you can do. > > You can do a similar thing on Linux to get reports off desktop B2G: > > $ kill -34 $(pidof b2g) > $ cd /tmp > $ gunzip the-memory-report-for-the-pid-you-want.gz > > and load this file into about:memory, as above. It will only have one > process's memory reports, unlike merged-reports above. > > I don't have a solution at the moment for those of you on Mac and > Windows. Sorry. :( > > I'm working on a number of improvements here, including > > * Automatically opening merged-reports in Firefox. > * Allowing you to dump b2g's gc/cc logs. > * Better support on desktop > * Better documentation in get-about-memory.py. > > But much of this work is taking a backseat to other basecamp-blocking > work I'm doing, so please don't hold your breath. If you need > anything in particular to do your job more effectively, let me know. > Patches are, of course, welcome. :) > > I'm also available to assist in interpreting memory reports. Other > people who can help include njn, mccr8, and khuey. Note that if you > hover over any item in about:memory, the tooltip will show a > description of that particular reporter. > > Happy profiling, > -Justin _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
