Closed Bug 2003998 Opened 11 months ago Closed 11 months ago

0.27 - 0.26% Base Content JS / Base Content JS (OSX, Windows) regression on Thu November 27 2025

Categories

(Core :: JavaScript: Standard Library, defect)

defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Perfherder has detected a awsy performance regression from push 7710efd65beca1f9b7ba01297f9ff6b3ac4b8cc0. 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 bacasandrei@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.27% Base Content JS macosx1470-64-shippable fission 1,587,522.00 -> 1,591,760.00
0.26% Base Content JS windows11-64-24h2-shippable fission 1,589,424.00 -> 1,593,488.00

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask bacasandrei@mozilla.com to do that for you.

You can run all of these tests on try with ./mach try perf --alert 47706

The following documentation link provides more information about this command.

Flags: needinfo?(andrebargull)

Bug 1955545 modified self-hosting code, which can result in Base Content JS changes. So this is a WONT FIX.

Status: NEW → RESOLVED
Closed: 11 months ago
Flags: needinfo?(andrebargull)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.