187
edits
Firefox OS/Performance/Debugging OOMs: Difference between revisions
Jump to navigation
Jump to search
Firefox OS/Performance/Debugging OOMs (view source)
Revision as of 18:15, 18 June 2013
, 18 June 2013→Step 2: Collect memory reports
| Line 49: | Line 49: | ||
After you've verified that your crash is actually due to OOM, the next step is to collect a memory report from the phone before the app crashes. A memory report will help us understand where memory is being used. | After you've verified that your crash is actually due to OOM, the next step is to collect a memory report from the phone before the app crashes. A memory report will help us understand where memory is being used. | ||
This step is a bit tricky, because once an app crashes, there's no way to collect a memory report from that process. There's no way to trigger a memory report when the kernel tries to kill a process -- by then, it's too late. | This step is a bit tricky, because once an app crashes, there's no way to collect a memory report from that process. There's also no way to trigger a memory report when the kernel tries to kill a process -- by then, it's too late. | ||
To pull a memory report from the phone, first update your tree so you get the latest version of this tool. <tt>repo sync</tt> is not sufficient. | To pull a memory report from the phone, first update your tree so you get the latest version of this tool. <tt>repo sync</tt> is not sufficient. | ||