0.15% installer size (Windows) regression on Tue October 28 2025
Categories
(Core :: Security: PSM, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox144 | --- | unaffected |
| firefox145 | --- | unaffected |
| firefox146 | --- | affected |
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Regression)
Details
(Keywords: perf-alert, regression)
Perfherder has detected a build_metrics performance regression from push 469a8d3f912c1dee15960b97b4f6a340b300ad24. As author of one of the patches included in that push, we need your help to address this regression.
Please acknowledge, and begin investigating this alert within 3 business days, or the patch(es) may be backed out in accordance with our regression policy. Our guide to handling regression bugs has information about how you can proceed with this investigation.
If you have any questions or need any help with the investigation, please reach out to afinder@mozilla.com. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.
Regressions:
| Ratio | Test | Platform | Options | Absolute values (old vs new) |
|---|---|---|---|---|
| 0.15% | installer size | windows2012-32-shippable | nightly | 111,642,342.96 -> 111,807,473.67 |
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.
You can run all of these tests on try with ./mach try perf --alert 47277
The following documentation link provides more information about this command.
|
||
Updated•6 months ago
|
|
||
Comment 1•6 months ago
|
||
Set release status flags based on info from the regressing bug 1994306
|
||
Comment 2•6 months ago
|
||
The size increase comes from the list of QWAC trust anchors. It's already about as small as it can be, so I don't think there's really anything we can do here.
Description
•