1650436 - Janky scrolling on bose.com with WebRender enabled

Status: NEW

(Core :: Graphics: WebRender, defect, P3)

Description

[Emilio Cobos Álvarez [:emilio]]

(I started filing this as a perf bug, thus the template)

Basic information

Steps to Reproduce: Load https://www.bose.com/en_us/support/article/no-sound-from-connected-device0.html. This is more noticeable in Android / GeckoView, but also happens in desktop, both with and without WR.

Expected Results: Smooth scrolling.

Actual Results: Scrolling janks

More information

Happens with and without WR enabled.

Profile URL: https://share.firefox.dev/3dVVahj (there doesn't seem to be much going on there unfortunately...).

Given scrolling is not janky when scrolling with keyboard, I suspect this may be a site issue... 68 definitely seems much snappier than nightly. I'm not on a good enough connection to do a proper bisection right now.

Comment 1

[Emilio Cobos Álvarez [:emilio]]

75 looks good too.

Comment 2

[Emilio Cobos Álvarez [:emilio]]

Hmm... Though now I don't seem to consistently repro on desktop... I can repro on my profile always though... On android nightly the page is pretty unusable :(

Comment 3

[Emilio Cobos Álvarez [:emilio]]

Ah, my android device now uses WR by default, which explains why I thought that this reproed with and without WR (I thought I initially had it disabled), and that I could repro on desktop on my profile but not while running mozregression.

On Android this page kills Firefox's performance.

Comment 4

[Emilio Cobos Álvarez [:emilio]]

https://share.firefox.dev/2YUz3Dy is a hopefully more useful profile from desktop.

Comment 5

[Cristian Fogel [:cfogel]]

Managed to reproduce the issue on a device with macOS 10.15.5 as well.

Regression range, picked up manually:

• Last good: 2020-06-18-21-28-28
• First bad: 2020-06-19-09-21-44
• Pushlog: URL

Comment 6

[Pascal Chevrel (relman team) -> :pascalc]

Marking 79 as affected per the regression range.

Comment 7

[Jeff Muizelaar [:jrmuizel]]

Christian, can you get a tighter regression range?

Comment 8

[Cristian Fogel [:cfogel]]

This was the best I could get; limitations being that it didn't seem to reproduce via mozregression which I found odd.
Checked with people from our Mobile team and they're limited to manually getting the regression ranges as well.

Let me know if there is something I can help you with, to push this further.

Comment 9

[Kartikaya Gupta (email:[e-mail])]

Loading this page in GVE with WR enabled on a Pixel2 totally destroys the browser. It starts to load, then either goes white right away or on scrolling, and nothing else loads after that. It was happening on the 2020-06-17 and 2020-06-01 builds as well so I'm not sure how much I trust the regression range from macOS. bug 1654852 is making it hard for me to actually use mozregression for this.

Comment 10

[Kartikaya Gupta (email:[e-mail])]

Even seeing it on the 2020-01-01 GVE build.

Comment 11

[Jim Mathies [:jimm]]

Kats, should we be tracking this for release builds? The priority is low but your last comment makes this sounds pretty bad.

Comment 12

[Kartikaya Gupta (email:[e-mail])]

It is bad, but it's not a recent regression. It's probably worth tracking and prioritizing though.

Comment 13

[Jim Mathies [:jimm]]

From Kats - might have to do with blob images. May be a dupe of Bug 1662297 - Zillow using massive amounts of memory.

Comment 14

[James Graham [:jgraham]]

I tried to reproduce this, but couldn't. Emilio: can you still repro? Otherwise I think we close it as WFM.