Confirmed users, Bureaucrats and Sysops emeriti
2,088
edits
Gaia/Hacking: Difference between revisions
Jump to navigation
Jump to search
→Tips
Ptheriault (talk | contribs) |
(→Tips) |
||
| Line 252: | Line 252: | ||
* If this doesn't fix it, check if there is any other process listening on port 8080. The default profile of gaia starts httpd.js, which listens on port 8080. When running a debug profile, b2g connects to localhost:8080. If some other process is running on port 8080, b2g will fail to display the home screen of gaia | * If this doesn't fix it, check if there is any other process listening on port 8080. The default profile of gaia starts httpd.js, which listens on port 8080. When running a debug profile, b2g connects to localhost:8080. If some other process is running on port 8080, b2g will fail to display the home screen of gaia | ||
** To find out if this is the case, you can enable logging on httpd.js. The httpd.js in the profile resides in this location - $GAIA/profile/extensions/httpd/content/httpd.js. Edit the variable var DEBUG=false; to change the DEBUG to true. Save the file and restart b2g. On the console now, you will be able to view the httpd's logs | ** To find out if this is the case, you can enable logging on httpd.js. The httpd.js in the profile resides in this location - $GAIA/profile/extensions/httpd/content/httpd.js. Edit the variable var DEBUG=false; to change the DEBUG to true. Save the file and restart b2g. On the console now, you will be able to view the httpd's logs | ||
=== Diagnosing OOM problems === | |||
[https://bugzilla.mozilla.org/show_bug.cgi?id=798747#c7 From Cjones]: | |||
Another way to diagnose possible OOMs is to open a terminal and run | |||
$ watch -n 1 'adb shell b2g-procrank' | |||
If you see the "USS" of one of the app processes go up near 100MB and then that process disappear from the process list (accompanied by some sort of visual crash in gaia), then you've almost certainly seen an OOM kill. | |||