Closed Bug 2047135 Opened 1 month ago Closed 1 month ago

6.4 - 5.61% jetstream3 cdjs-Average + 3 more (OSX) regression on Tue June 9 2026

Categories

(Firefox Build System :: Toolchains, defect)

defect

Tracking

(firefox-esr140 unaffected, firefox151 unaffected, firefox152 unaffected, firefox153 affected)

RESOLVED DUPLICATE of bug 2046376
Tracking Status
firefox-esr140 --- unaffected
firefox151 --- unaffected
firefox152 --- unaffected
firefox153 --- affected

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Perfherder has detected a browsertime performance regression from push f310e997ae26a071d423bd408830fd8934027242. 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.

Regression Test Platform Options Absolute values [old vs new]
6% jetstream3 cdjs-Average (doc) macosx1470-64-shippable fission webrender 80.76 -> 85.93
6% jetstream3 cdjs-Worst (doc) macosx1470-64-shippable fission webrender 83.59 -> 88.78
6% jetstream3 cdjs-Average (doc) macosx1500-aarch64-shippable fission webrender 23.51 -> 24.86
6% jetstream3 cdjs-Geometric (doc) macosx1470-64-shippable fission webrender 59.45 -> 56.11

Support & Actionable Steps

For questions, please contact fbilt@mozilla.com. You can also find help on Slack (#perf-help) or Matrix (#perftest).

Action guide details:

Flags: needinfo?(mh+mozilla)

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

Considering webrender is using smallvec, it's very possible it's the same underlying thing as bug 2046376. Let's see how things go after the fix for that one lands.

Status: NEW → RESOLVED
Closed: 1 month ago
Duplicate of bug: 2046376
Flags: needinfo?(mh+mozilla)
Resolution: --- → DUPLICATE

Huh. But isn't Jetstream supposed to be a JS benchmark? If webrender affects it it seems bad...

You need to log in before you can comment on or make changes to this bug.