Necko: Electrolysis design and subprojects: Difference between revisions

Necko: Electrolysis design and subprojects (view source)

332 bytes added , 24 May 2010

Confirmed users

431

edits

@@ Line 52: / Line 52: @@
 === Running ===
-The necko e10s code is currently turned off by default (instead each child process gets its own full necko stack).  To turn it on, set NECKO_E10S_HTTP=1 in your environment.
+The necko e10s code is currently turned on by default in the e10s tree.  You can also revert to our starting point mode, where each child process gets its own full necko stack (more feature-complete, but takes up more memory, and separate processes will not have a synchronized cookie database), by setting NECKO_SEPARATE_STACKS in your environment).  This is mainly useful only if you're trying to test something other than necko, but the e10s/necko code doesn't yet implement some feature that you need.
 Depending on what you're trying to do, you'll either be running [https://developer.mozilla.org/en/Writing_xpcshell-based_unit_tests xpcshell] tests or the [https://wiki.mozilla.org/Content_Processes/Build remote tab demo] (a.k.a. test-ipc.xul).   Running xpcshell tests is quite lightweight (text-based, and fewer XPCOM things to load, so fast to run on a remote machine over ssh, etc.), while test-ipc.xul fires up a version of the whole browser.  Develop with xpcshell when you can (unfortunately some important features--like load groups, notifications, etc.--are not tested by xpcshell, so you currently need to run test-ipc.xul).