1514524 - 65.0b3 Slow to open new tabs when first opening the browser

Status: NEW

(Firefox :: General, defect, P3)

Description

[mrbridgesix]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

When first opening the browser there is some slow down in the animation to create new tabs, started happening as soon as FF updated to 65.0b3 and persists on 65.0b4.

Completely clean reinstalled the browser with new profile and no extensions issue persists.

Issue is not present in FF 64.

Turning off hardware acceleration fixes the issue.

PC specs: W10 1803, GTX 1060 6GB (417.35), i5 8400 and 16GB of RAM.

Comment 1

[Stefan [:StefanG_QA]]

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0 20181217180946

I've tested this report on Windows 10 x64 using the latest Nightly, Beta and Fx release builds. I see some slow down in the new tab animation when starting the browser with a new profile and HWA enabled. When HWA is disabled the issue does not reproduce.

Comment 2

[Lee Salzman [:lsalzman]]

Could you check using mozregression (https://mozilla.github.io/mozregression/) which patch it might have been that caused this regression? This would greatly help us to narrow down the cause.

Comment 3

[mrbridgesix]

I'm not familiar with the mozregression tool but mine looked like that after testing with the dafault 1 year window.

https://drive.google.com/file/d/1uyTbLfa16H6ZbjZv2K0fq-C-r0NWUzOP/view

Comment 4

[Lee Salzman [:lsalzman]]

It seems mozregression has pegged bug 1511465 as the cause of this. Dave, Can you look into this?

Comment 5

[Dave Townsend [:mossop]]

That bug only changed an automated test that doesn't ship with the browser. It's physically impossible for it to have affected how the browser runs.

Comment 6

[Ryan VanderMeulen [:RyanVM]]

Stefan, can you please try to find a regression range? And reporter, can you look at about:studies and see if you're being opted into the WebRender trials?

Comment 7

[Stefan [:StefanG_QA]]

Here are my findings: 

Last good revision: 5c3e0fc819ba0da8cdcd85eb16cedcb9d2c8f81e
First bad revision: d835874be99afb421be275d5ed04b1a050458977
Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=5c3e0fc819ba0da8cdcd85eb16cedcb9d2c8f81e&tocha
nge=d835874be99afb421be275d5ed04b1a050458977

I've got 4 different regression ranges from 4 tries. Some of the older builds are crashing during startup when I`m using the profile with which I was able to reproduce the issue.

Comment 8

[Stefan [:StefanG_QA]]

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=5c3e0fc819ba0da8cdcd85eb16cedcb9d2c8f81e&tochange=d835874be99afb421be275d5ed04b1a050458977

Comment 9

[Ryan VanderMeulen [:RyanVM]]

Hrm, that wouldn't explain the regression seen on Beta, though, since bug 1472212 is still behind a Nightly-only pref :\. Unless there's some non-ifdeffed changes there which are relevant somehow...

Comment 10

[mrbridgesix]

In my current profile I've not participated in any studies and no new studies should run because I've manually disabled them, yet the issue is still present.

Note: I'm always able to reproduce the issue with a new profile and standard settings be it in beta or nightly.

Comment 11

[Jared Wein [:jaws] (please needinfo? me)]

Hi mrbridgesix, are there are any specific pages you are opening after startup? Or are they blank newtab pages?

Comment 12

[mrbridgesix]

My browser is set to start at the about:newtab page, it opens fine and all but the first ctrl+t/newtab (about:newtab) after the initial one be it from the initial about:newtab or a website, as long as there is only one tab open, on that browser session it causes the actual animation of the top bar to not display correctly, after that the animations are fine.

Changed my home and newtab to about:blank issue persists exact same behaviour.

My uneducated guess is that the issue is time based or gpu clock related because after reproducing the issue I can cause all the subsequent newtab opening and closing animations to lag but after 2-3 seconds they are all fine...

Comment 13

[Liz Henry (:lizzard) (relman/hg->git project)]

Happy to take a patch in nightly 67, or potentially, in beta 66 for this.
I'm marking it fix-optional to remove it from weekly regression triage, since it has a priority assigned.