Closed
Bug 1495628
Opened 7 years ago
Closed 7 years ago
Launcher process: Consider --disable-e10s to also disable the launcher process in local builds
Categories
(Firefox :: General, enhancement, P3)
Tracking
()
RESOLVED
INVALID
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | affected |
People
(Reporter: bugzilla, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: inj+)
This has been requested on dev-platform.
We could do this for local developer builds.
|
||
Comment 1•7 years ago
|
||
or a hidden pref to disable it (like we can disable e10s by setting browser.tabs.remote.autostart to false)
|
|
||
Comment 2•7 years ago
|
||
I see that I can build with --disable-launcher-process that would be a sufficient work-around for now
|
Reporter | |
Comment 3•7 years ago
|
||
(In reply to Jean-Yves Avenard [:jya] from comment #2)
I see that I can build with --disable-launcher-process that would be a
sufficient work-around for now
Yeah, I think that this is sufficient for everybody; launcher process is really orthogonal to e10s anyway.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•