Firefox OS/Performance/Debugging OOMs: Difference between revisions

Firefox OS/Performance/Debugging OOMs (view source)

No change in size , 20 June 2013

m

Confirmed users

561

edits

@@ Line 89: / Line 89: @@
 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; 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.
+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 you're 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.