Closed
Bug 1124961
Opened 9 years ago
Closed 8 years ago
Add a ./mach run --no-e10s flag
Categories
(Firefox Build System :: Mach Core, enhancement)
Tracking
(e10s-)
RESOLVED
DUPLICATE
of bug 1287069
Tracking | Status | |
---|---|---|
e10s | - | --- |
People
(Reporter: ehsan.akhgari, Assigned: arai)
Details
Attachments
(1 file)
5.17 KB,
patch
|
Details | Diff | Splinter Review |
Many times when rebuilding after pulling, the objdir gets clobbers, so I end up with a fresh profile (which is fine) which is going to start in e10s mode. That is super annoying if you want to debug and are not looking to debug e10s related issues. It would be nice to add a --no-e10s command line argument which sets up the right prefs for Firefox to start in non-e10s mode.
Updated•9 years ago
|
tracking-e10s:
--- → -
Assignee | ||
Comment 1•8 years ago
|
||
Added --e10s option, with 'on' or 'off' choices. Specifying the option creates or updates prefs.js inside profile directory. it removes existing 'browser.tabs.remote.autostart.2' pref, and adds the same pref with true for 'on' or false for 'off'. So that --e10s=off disables e10s for new profile, or pre-existing profile with e10s enabled. and --e10s=on enables e10s for new profile, or pre-existing profile with e10s disabled. for now, this option works only for 'scratch_user'.
Comment 2•8 years ago
|
||
I didn't realize there is an existing bug... So I submitted a patch in bug 1287069 which adds a new environment so that it doesn't need to touch the prefs, which makes that patch look simplier than this one (I think). Given the reviewer of both patches is gps, it's all up to him :)
Comment 3•8 years ago
|
||
Bug 1287069 got landed. Let's mark this bug duplicate of that.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•8 years ago
|
Attachment #8771339 -
Flags: review?(gps)
Updated•6 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•