6.04 - 3.32% tresize / tresize + 2 more (Linux) regression on Tue June 8 2021
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr78 | --- | unaffected |
| firefox-esr91 | --- | wontfix |
| firefox89 | --- | unaffected |
| firefox90 | --- | unaffected |
| firefox91 | --- | wontfix |
| firefox92 | --- | wontfix |
| firefox93 | --- | wontfix |
People
(Reporter: alexandrui, Unassigned)
References
(Regression)
Details
(4 keywords, Whiteboard: [fxperf:p3] fixed by bug 1786513)
Perfherder has detected a talos performance regression from push ad71dde9ed5e28957b124001a78c88fc1d94426a. As author of one of the patches included in that push, we need your help to address this regression.
Regressions:
| Ratio | Suite | Test | Platform | Options | Absolute values (old vs new) |
|---|---|---|---|---|---|
| 6% | tresize (docs) | linux1804-64-shippable-qr | e10s stylo webrender | 20.65 -> 21.89 | |
| 6% | tresize (docs) | linux1804-64-shippable | e10s stylo | 18.48 -> 19.56 | |
| 5% | tresize (docs) | linux1804-64-shippable | e10s stylo | 18.51 -> 19.48 | |
| 3% | tresize (docs) | linux1804-64-shippable-qr | e10s stylo webrender-sw | 20.70 -> 21.39 |
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 offending patch(es) will be backed out in accordance with our regression policy.
For more information on performance sheriffing please see our FAQ.
Comment 1•5 years ago
|
||
Set release status flags based on info from the regressing bug 1695472
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Comment 2•5 years ago
|
||
tresize looks to be better now than it was prior to this regressing. Not sure how actionable this is going to be at this point.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 3•2 years ago
|
||
Bug 1786513 fixed what likely caused the regression here, by going back to a resize event handler instead of a ResizeObserver.
Updated•2 years ago
|
Description
•