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 21:03, 20 June 2013
, 20 June 2013→Step 2: Collect memory reports
No edit summary |
|||
| Line 77: | Line 77: | ||
If you don't have access to a device with more RAM, you can try to run get_about_memory.py just before the app crashes. Again, you can run b2g-info in a loop to figure out when to run get_about_memory.py. | If you don't have access to a device with more RAM, you can try to run get_about_memory.py just before the app crashes. Again, you can run b2g-info in a loop to figure out when to run get_about_memory.py. | ||
==== Step 2, option 3: Run B2G on your desktop ==== | ==== Step 2, option 3: Use a smaller testcase ==== | ||
We often hit OOMs when doing something like "load a file of size at least X in the app." | |||
If the app crashes very quickly with a testcase of size X, you could try running a similar but smaller testcase (say, size X/2) and capturing a memory report after that succeeds. The memory report generated this way often gives us good insight into the OOM crash that we ultimately care about. | |||
==== Step 2, option 4: Run B2G on your desktop ==== | |||
If worst comes to worst, you can run B2G on your desktop, which probably has much more RAM than your FFOS phone. This is tricky because B2G running on a desktop machine is a different in some key ways from B2G running on a phone. | If worst comes to worst, you can run B2G on your desktop, which probably has much more RAM than your FFOS phone. This is tricky because B2G running on a desktop machine is a different in some key ways from B2G running on a phone. | ||