21.92% google-mail fcp (Linux) regression on Wed September 9 2026
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox-esr153 | --- | unaffected |
| firefox156 | --- | unaffected |
| firefox157 | --- | unaffected |
| firefox158 | --- | wontfix |
People
(Reporter: performance-sheriff-bot, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression, Whiteboard: [autowebcompat:processed][autowebcompat:repro-failed])
User Story
autowebcompat-repro-status:failed autowebcompat-repro-reason:not_web_platform
Perfherder has detected a browsertime performance regression from push 4e4323316e424e2bc35932b6c354e43f386b5ce1. 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] | Performance Profiles |
|---|---|---|---|---|---|
| 22% | google-mail fcp (doc) | linux2404-64-shippable | cold fission webrender | 171.47 -> 209.06 | Before/After |
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:
- See the guide to handling regression bugs for investigation steps.
- Review the alert summary for affected tests, graphs, and comparisons.
- Check the PerfCompare results.
- Tests on Try: Run all tests using
./mach try perf --alert 52755(See documentation link for details). - Test locally: To run the tests locally use
./mach perftest 52755 - Profiling jobs: Trigger jobs from Treeherder job view or request them from fbilt@mozilla.com.
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Comment 1•2 months ago
|
||
:smaug, since you are the author of the regressor, bug 2062317, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 2•2 months ago
|
||
bug 2062317 was backed out. BugBot, you should realize that.
Comment 3•2 months ago
|
||
Regressor has been backed out, so I'll close this.
Comment 4•2 months ago
|
||
Set release status flags based on info from the regressing bug 2062317
Updated•1 month ago
|
Comment 5•1 month ago
•
|
||
I'm gonna reopen this, because the regression is still there. Also the suspected regressor re-landed on 2026-09-17
:smaug i think it actually had the opportunity to land briefly on central before being backed out (https://hg.mozilla.org/mozilla-central/rev/4e4323316e42) and thats why it prob got confused.
Updated•1 month ago
|
Comment 6•1 month ago
|
||
Yeah, there isn't much we can do. Either we have the webcompat issue or perf regression (well, that is really a scheduling change)
Updated•1 month ago
|
Description
•