Confirmed users
1,345
edits
Firefox OS/Performance/Debugging OOMs: Difference between revisions
Firefox OS/Performance/Debugging OOMs (view source)
Revision as of 04:08, 19 November 2013
, 19 November 2013→Step 3: Analyze the memory report
Digitarald (talk | contribs) No edit summary |
Nnethercote (talk | contribs) |
||
| Line 109: | Line 109: | ||
When you run get_about_memory.py, it will open a memory report in Firefox. This file contains information about the memory usage of all processes on the system. | When you run get_about_memory.py, it will open a memory report in Firefox. This file contains information about the memory usage of all processes on the system. | ||
Reading these reports can be a bit overwhelming at first, but it's not so bad once you get the hang of it. | Reading these reports can be a bit overwhelming at first, but it's not so bad once you get the hang of it. You can click on a sub-tree to collapse (or expand) it, and you can hover over any leaf node to get a description of what that node describes. | ||
What you're looking for is something "unusually large" in the crashing process. You can get an idea of what "unusually large" means by capturing a memory report of your app when it's not using a ton of memory and comparing that to the errant memory report. | What you're looking for is something "unusually large" in the crashing process. You can get an idea of what "unusually large" means by capturing a memory report of your app when it's not using a ton of memory and comparing that to the errant memory report. | ||