Forum Discussion
Dev channel update to 80.0.361.5 is live
I've sent 3-4 Smiley reports about this bug, but thought I'd post it here, too, in case anyone else has experienced this.
A very unusual bug where page contents, after being rendered, aren't cached. So if you scroll too fast, the entire page is re-drawn as you scroll (!). Especially noticeable on longer pages. Have not seen this before, until this most recent build.
To a normal user, it just looks/feels like an ancient 1990s browser that can't keep up with modern websites. It's often fixable with a restart, but that gets old.
See a short video here: https://streamable.com/iritz
System:
i5-8600K (monitor above is powered by the UHD 630 iGPU; driver 26.20.100.7584)
32 GB DDR4-3200
Samsung 960 EVO 250 GB
1920 x 1080 @ 60Hz
Windows 10 Pro x64 1909 (18363.535)
What I've tried:
- Restarting does fix it for a few minutes.
- Turning off hardware acceleration reduces its severity, but it's still present.
- Reproducible on any long page.
- Reproducible in inPrivate windows.
I believe this latest build has been the only build I've experienced it.
So if you scroll too fast, the entire page is re-drawn as you scroll (!).
ikjadoon Scrolling is one of the areas that we know Chromium was less smooth compared to Edge Legacy, and while we've started making investments in this area, there's still a lot of work we want to do. I'd be very curious if you can get the same thing to happen in Chrome, since it's very likely we're inheriting this from them.
josh_bodner Here's what I've found. You're exactly right, inherited from Chromium Beta 80.0.3xxxx.x builds.
- Chrome Stable (Chromium 79.0.3945.88): no bug
- Edge Dev (prior Chromium 80.0.355.1): no bug (IIRC)
- Chrome Beta (Chromium 80.0.3987.16): scroll repaint bug
- Edge Dev (Chromium 80.0.361.5/9): scroll repaint bug
- Chrome Dev (Chromium 81.x.x.x): no bug
- Legacy Edge Stable (44.18362.449.0): no bug
- Firefox Stable (71.0): no bug
- Internet Explorer Stable (11.535.18362.0): no bug
The bug has been fixed in Chrome Dev (81). Once Edge Chromium stable launches, I imagine it'll be Stable 79 / Beta 80 / Dev 81 / Canary 82. For the beta testers, maybe the Beta 80 build will be updated so it doesn't exhibit the same bug from our Dev 80 build.
ikjadoon good investigation work! Canary and Dev usually have the same major build number, so they're both 81 right now (or at least, they will be after our next Dev update. The only time they differ is the week or so between the last Dev build of a particular major number, but that week this time just happened to fall on the couple of weeks during the holidays when we weren't publishing a new Dev build!)
