Closed Bug 1883053 Opened 8 months ago Closed 8 months ago

4.01 - 3.65% google-slides FirstVisualChange / google-slides FirstVisualChange + 1 more (OSX) regression on Sun February 25 2024

Categories

(Core :: Graphics: WebRender, defect)

defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox-esr115 --- unaffected
firefox123 --- unaffected
firefox124 --- unaffected
firefox125 --- affected

People

(Reporter: bacasandrei, Unassigned)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Perfherder has detected a browsertime performance regression from push b9f2c3f5a805a94fdebf367e5e0bdb964074a3e7. As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

Ratio Test Platform Options Absolute values (old vs new) Performance Profiles
4% google-slides FirstVisualChange macosx1015-64-shippable-qr cold fission webrender 924.12 -> 961.18 Before/After
4% google-slides FirstVisualChange macosx1015-64-shippable-qr cold fission webrender 922.77 -> 959.28 Before/After
4% google-slides FirstVisualChange macosx1015-64-shippable-qr bytecode-cached cold fission webrender 936.65 -> 970.86 Before/After

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests. Please follow our guide to handling regression bugs and let us know your plans within 3 business days, or the patch(es) may be backed out in accordance with our regression policy.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

You can run these tests on try with ./mach try perf --alert 41599

For more information on performance sheriffing please see our FAQ.

Flags: needinfo?(gwatson)

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

This change is a required bug fix, and a small perf regression in some tests is expected.

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