Closed Bug 1745963 Opened 3 years ago Closed 3 years ago

Running Firefox from `./mach run` forces Fission to be disabled

Categories

(Firefox Build System :: General, defect, P2)

defect

Tracking

(firefox-esr91 unaffected, firefox95 unaffected, firefox96 unaffected, firefox97 fixed)

RESOLVED FIXED
Tracking Status
firefox-esr91 --- unaffected
firefox95 --- unaffected
firefox96 --- unaffected
firefox97 --- fixed

People

(Reporter: mconley, Assigned: gbrown)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [fixed by bug 1744091])

STR:

  1. Create a new local build of Firefox
  2. Run it with ./mach run
  3. Open the Browser Console, and type in: Services.appinfo.fissionAutostart and press enter

ER:

It should return true.

AR:

It returns false.

It seems that when we launch Firefox from ./mach run, Fission is being force-disabled. It can be re-enabled with ./mach run --enable-fission, but that seems non-obvious and probably the wrong default.

I suspect this is a regression from 1732358.

No longer blocks: 1732358
Regressed by: 1732358
Has Regression Range: --- → yes

Hey ahal, is there some mach stuff needed to make Fission-enabled be the default state for local builds?

Flags: needinfo?(ahal)

We should probably replace the --enable-fission with --disable-fission

For test harnesses this is being tracked in bug 1744091. I'll admit mach run wasn't on my radar, it's probably more of an Engineering Workflow item.. but maybe we can fix this one at the same time?

Flags: needinfo?(ahal)
See Also: → 1744091

This should be as simple as flipping around the argument and then the check here: https://hg.mozilla.org/mozilla-central/file/6a8175e7c32b19d28ab4fa35b3eb385418234b20/python/mozbuild/mozbuild/mach_commands.py#l1781. Unfortunately the arguments are shared between desktop and android, which still has fission disabled, so we may need to instead add a second enable_fission argument and then flip the prefs based on which is passed, setting MOZ_FORCE_DISABLE_FISSION to disable, and MOZ_FORCE_ENABLE_FISSION to enable (or nothing if no flag is passed)

Set release status flags based on info from the regressing bug 1732358

Rating could be even S4 from users perspective, but it is a possible source of confusion for developers, thus the P2/S3.

Severity: -- → S3
Priority: -- → P2
Component: DOM: Content Processes → General
Product: Core → Firefox Build System

This should be working now: 'mach run' (desktop) runs firefox with fission enabled; use --fission-disable to disable.

Assignee: nobody → gbrown
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
See Also: 1744091
Depends on: 1744091
Resolution: DUPLICATE → FIXED
Whiteboard: [fixed by bug 1744091]
You need to log in before you can comment on or make changes to this bug.