3.46% bing FirstVisualChange (Android) regression on Mon February 9 2026
Categories
(Firefox for Android :: Homepage, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox148 | --- | unaffected |
| firefox149 | --- | wontfix |
| firefox150 | --- | affected |
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a browsertime performance regression from push a0b3b185c11153f04cc600403b4e1210a5635c1d. 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 |
|---|---|---|---|---|---|
| 7% | bing fcp (doc) | android-hw-a55-14-0-aarch64-shippable | cold webrender | 261.02 ms -> 280.15 ms | |
| 3% | bing FirstVisualChange (doc) | android-hw-a55-14-0-aarch64-shippable | cold webrender | 676.79 -> 700.20 |
| Improvements | Test | Platform | Options | Absolute values [old vs new] | Performance Profiles |
|---|---|---|---|---|---|
| 15% | speedometer3 TodoMVC-JavaScript-ES5/Adding100Items/Async (doc) | linux1804-64-shippable-qr | fission webrender | 6.19 ms -> 5.28 ms | Before/After |
| 13% | sina fcp (doc) | android-hw-a55-14-0-aarch64-shippable | cold webrender | 469.08 ms -> 406.67 ms | |
| 11% | bing largestContentfulPaint (doc) | android-hw-a55-14-0-aarch64-shippable | warm webrender | 144.98 ms -> 128.41 ms | |
| 11% | bing fcp (doc) | android-hw-a55-14-0-aarch64-shippable | warm webrender | 144.10 ms -> 127.62 ms | |
| 11% | speedometer3 TodoMVC-JavaScript-ES5/Adding100Items/Async (doc) | android-hw-a55-14-0-aarch64-shippable | webrender | 9.48 ms -> 8.44 ms | |
| ... | ... | ... | ... | ... | ... |
| 3% | sina ContentfulSpeedIndex (doc) | android-hw-a55-14-0-aarch64-shippable | cold webrender | 2,352.51 ms -> 2,283.78 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:
- 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 48689(See documentation link for details). - Profiling jobs: Trigger jobs from Treeherder job view or request them from afinder@mozilla.com.
|
||
Comment 1•4 months ago
|
||
Set release status flags based on info from the regressing bug 2013312
|
||
Updated•4 months ago
|
|
|
||
Comment 2•3 months ago
|
||
It has been over 7 days with no activity on this performance regression.
:azinovyev, since you are the author of the regressor, bug 2013312, which triggered this performance alert, could you please provide a progress update?
If this regression is something that fixes a bug, changes the baseline of the regression metrics, or otherwise will not be fixed, please consider closing it as WONTFIX. See this documentation for more information on how to handle regressions.
For additional information/help, please needinfo the performance sheriff who filed this alert (they can be found in comment #0), or reach out in #perftest, or #perfsheriffs on Element.
For more information, please visit BugBot documentation.
|
||
Comment 3•3 months ago
|
||
2013312 is a mechanical change that helps reduce code complexity. Given the performance wins and losses, it might even out the performance costs.
Description
•