Firefox OS/Performance/Debugging OOMs: Difference between revisions

Jump to navigation Jump to search
(Created page with "== How to debug a B2G OOM crash== B2G runs on severely memory-constrained devices, and it's easy for apps to exhaust the memory available on the system. When a process exhau...")
 
Line 81: Line 81:
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.


In particular, B2G on desktop machines has multiprocess disabled by default.  It doesn't really work 100% correctly anywhere, but it mostly works on Linux and Mac.  (I'm not sure yet how to enable it.)
In particular, B2G on desktop machines has multiprocess disabled by default.  It doesn't really work 100% correctly anywhere, but it mostly works on Linux and Mac.  (I'm not sure yet how to enable it; for now, ask on #b2g and please update the wiki if you figure it out.) You can test on your desktop without multiprocess enabled, but in my experience a lot of our high memory usage issues are caused by our inter-process communication code, so that won't necessarily trigger the bug your'e seeing.


It's also not as convenient to take memory reports from a B2G desktop process.  On Linux, you can send signal 34 to the main B2G process and we'll write "memory-report-*.gz" files out to /tmp.
It's also not as convenient to take memory reports from a B2G desktop process.  On Linux, you can send signal 34 to the main B2G process and we'll write "memory-report-*.gz" files out to /tmp.
187

edits

Navigation menu