2.99 - 2.02% speedometer3 NewsSite-Next/NavigateToPolitics/Sync / speedometer3 NewsSite-Next/NavigateToUS/Sync + 1 more (Android) regression on Fri January 30 2026
Categories
(Firefox for Android :: Performance, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox147 | --- | unaffected |
| firefox148 | --- | unaffected |
| firefox149 | --- | fix-optional |
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a browsertime performance regression from push c5c3971b66d0459595612ae7b194f5ae03a9b161. 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] |
|---|---|---|---|---|
| 3% | speedometer3 NewsSite-Next/NavigateToPolitics/Sync (doc) | android-hw-a55-14-0-aarch64-shippable | fission webrender | 57.01 -> 58.72 |
| 2% | speedometer3 NewsSite-Next/NavigateToWorld/Sync (doc) | android-hw-a55-14-0-aarch64-shippable | fission webrender | 61.02 -> 62.48 |
| 2% | speedometer3 NewsSite-Next/NavigateToUS/Sync (doc) | android-hw-a55-14-0-aarch64-shippable | fission webrender | 69.31 -> 70.71 |
Support & Actionable Steps
For questions, please contact bacasandrei@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 48538(See documentation link for details). - Profiling jobs: Trigger jobs from Treeherder job view or request them from bacasandrei@mozilla.com.
Comment 1•9 months ago
•
|
||
The graphs are somewhat noisy, and identifying the exact cause is challenging. Could this revision possibly have contributed to the regression?
Comment 2•9 months ago
|
||
Set release status flags based on info from the regressing bug 2010698
Comment 3•8 months ago
|
||
It has been over 7 days with no activity on this performance regression.
:matt-tighe, since you are the author of the regressor, bug 2010698, 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 4•8 months ago
|
||
bug 2010698 includes no additional code in the production build of Firefox Android - it just sets up some unused modules in Android Components. it's impossible for me to see how this would have triggered a revision.
I also don't see a patch that I authored in the referenced pushlog: c5c3971b66d0459595612ae7b194f5ae03a9b161. Is this a tooling error?
Updated•8 months ago
|
Comment 5•8 months ago
|
||
Given the noise in the graphs, identifying the exact cause of the performance regression is challenging. If you are certain your recent changes are not responsible, I recommend closing this bug as invalid.
Updated•8 months ago
|
Comment 6•8 months ago
|
||
It has been over 7 days with no activity on this performance regression.
:matt-tighe, since you are the author of the regressor, bug 2010698, 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 7•8 months ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:kaya, since the bug has recent activity, could you have a look please?
For more information, please visit BugBot documentation.
Comment 8•8 months ago
|
||
It has been over 7 days with no activity on this performance regression.
:matt-tighe, since you are the author of the regressor, bug 2010698, 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.
Updated•8 months ago
|
Updated•8 months ago
|
Comment 9•8 days ago
|
||
Clearing the needinfo request since this bug has been closed as INVALID for 7 months and 21 days.
For more information, please visit BugBot documentation.
Description
•