Open Bug 2020567 Opened 6 days ago Updated 8 hours ago

13.35 - 6.46% perf_reftest coalesce-2.html + 2 more (Linux) regression on Tue February 24 2026

Categories

(Core :: DOM: Core & HTML, defect)

defect

Tracking

()

Tracking Status
firefox-esr140 --- unaffected
firefox148 --- unaffected
firefox149 --- unaffected
firefox150 --- affected

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Depends on 1 open bug, Regression)

Details

(4 keywords)

Perfherder has detected a talos performance regression from push 0d3fd295c1db2bbd7221f932cce34ae9043ebf3f. 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]
13% perf_reftest coalesce-2.html (doc) linux1804-64-shippable-qr e10s fission stylo webrender-sw 25.77 ms -> 29.21 ms
12% perf_reftest coalesce-2.html (doc) linux1804-64-shippable-qr e10s fission stylo webrender 26.52 ms -> 29.60 ms
6% perf_reftest coalesce-1.html (doc) linux1804-64-shippable-qr e10s fission stylo webrender-sw 77.56 ms -> 82.58 ms

Support & Actionable Steps

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

Action guide details:

Flags: needinfo?(emilio)

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

This is a microbenchmark that doesn't matter as much compared to the speedometer improvements from bug 2017005. Bug 2018923 would give this one back tho.

Depends on: 2018923
Flags: needinfo?(emilio)

Marking S3 to prioritize Speedometer 3.

Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.