1968988 - 32.59 - 2.04% bing-search-restaurants FirstVisualChange / youtube LastVisualChange + 79 more (Android) regression on Mon May 19 2025

Status: NEW

(GeckoView :: General, defect, P1)

Description

[Treeherder Bug Filer]

Perfherder has detected a browsertime performance regression from push d9908e2731bdeaf7a620c8e338ce7eac7563a75b. 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. Our guide to handling regression bugs has information about how you can proceed with this investigation.

If you have any questions or need any help with the investigation, please reach out to [e-mail]. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.

Regressions:

Ratio	Test	Platform	Options	Absolute values (old vs new)
33%	bing-search-restaurants FirstVisualChange	android-hw-a55-14-0-aarch64-shippable	warm webrender	109.87 -> 145.68
30%	google FirstVisualChange	android-hw-a55-14-0-aarch64-shippable	warm webrender	82.37 -> 106.73
30%	google ContentfulSpeedIndex	android-hw-a55-14-0-aarch64-shippable	warm webrender	82.38 -> 106.73
29%	google PerceptualSpeedIndex	android-hw-a55-14-0-aarch64-shippable	warm webrender	83.84 -> 107.83
26%	dailymail FirstVisualChange	android-hw-a55-14-0-aarch64-shippable	warm webrender	104.35 -> 131.63
26%	youtube FirstVisualChange	android-hw-a55-14-0-aarch64-shippable	warm webrender	90.35 -> 113.62
24%	dailymail PerceptualSpeedIndex	android-hw-a55-14-0-aarch64-shippable	warm webrender	110.55 -> 137.63
23%	google-search-restaurants FirstVisualChange	android-hw-a55-14-0-aarch64-shippable	warm webrender	103.75 -> 127.73
23%	wikipedia FirstVisualChange	android-hw-a55-14-0-aarch64-shippable	warm webrender	108.17 -> 132.72
22%	google fcp	android-hw-a55-14-0-aarch64-shippable	warm webrender	62.83 -> 76.87
...	...	...	...	...
6%	youtube SpeedIndex	android-hw-a55-14-0-aarch64-shippable	warm webrender	281.33 -> 297.03
4%	sina loadtime	android-hw-a55-14-0-aarch64-shippable	warm webrender	465.16 -> 483.88
3%	sina PerceptualSpeedIndex	android-hw-a55-14-0-aarch64-shippable	warm webrender	848.98 -> 872.72
2%	imdb PerceptualSpeedIndex	android-hw-a55-14-0-aarch64-shippable	warm webrender	2,052.30 -> 2,100.31
2%	youtube LastVisualChange	android-hw-a55-14-0-aarch64-shippable	warm webrender	770.79 -> 786.52

Improvements:

Ratio	Test	Platform	Options	Absolute values (old vs new)
3%	speedometer BackboneJS-TodoMVC/CompletingAllItems/Async	android-hw-a55-14-0-aarch64-shippable	webrender	8.60 -> 8.31

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask [e-mail] to do that for you.

You can run all of these tests on try with ./mach try perf --alert 45230

The following documentation link provides more information about this command.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 2

[Kaya [:kaya]]

Looking into this at the moment, please do not back out any patch, yet. Thanks!

Comment 3

[Donal Meehan [:dmeehan]]

Next week is the final week of beta for Fx140
Tracking for Fx140 since this was triaged as an S2.
:kaya, any concerns with addressing this in time?

Comment 4

[Kaya [:kaya]]

I'll put up a patch to enable SHIP nightly only and request an uplift of that. We will have SHIP enabled on Nightly while figuring out the issue with the performance. Then, we will re-enable it on all channels.

Comment 5

[Donal Meehan [:dmeehan]]

Setting Fx140 to disabled since Bug 1971562 was uplifted to beta

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

It has been over 7 days with no activity on this performance regression.

:kaya, since you are the author of the regressor, bug 1951246, 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

[Kaya [:kaya]]

The issue seems to be happening due to bfcache in parent. I am still debugging the flow.

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

It has been over 7 days with no activity on this performance regression.

:kaya, since you are the author of the regressor, bug 1951246, 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 9

[Kaya [:kaya]]

Getting useful performance profiles at the moment, will update once the root cause is determined.

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

It has been over 7 days with no activity on this performance regression.

:kaya, since you are the author of the regressor, bug 1951246, 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 11

[Markus Stange [:mstange]]

I would like to see a few before/after profiles in this bug. Do we know where the 35ms are spent? (those 35ms coming from the 109.87 -> 145.68 Bing regression)