1712396 - Main Renderer maxed-out after update

Status: RESOLVED WORKSFORME

(Core :: Graphics: WebRender, defect)

Description

[Holger]

Attachment: lag.mp4

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0

Steps to reproduce:

Installed FF89beta13 Developer Edition
loaded my productive profile (quite big)
kept it running for few days (suspending Laptop to RAM)
installed update to FF89beta15

Also happend for updates:

• beta8 -> beta9
• beta9 -> beta10 (explicit reboot at 2021-05-13 Do 01:20:25)
  did not happen for:
• beta10 -> beta11
• beta11 -> beta13

Actual results:

After update, FF starts itself in "slowmotion" The GUI has a noticeable lag of a few seconds (even after all page loads finished).

• The horizontal main menu blue highlight on "Datei Bearbeiten Ansicht ..." does not follow the mouse in timely manner (though the vertical performs better),
• dragging / resizing the window is jumpy,
• scrolling a page (e.g. a bug report here) is jumpy.
  See attached video and this profile
  https://share.firefox.dev/3bLxduS

Exiting Firefox and restarting it in the same KDE session, does not solve the issue:
https://share.firefox.dev/3v9cTuY

After rebooting the machine, performance is fine again.

Expected results:

FF should perform the same as it does after rebooting the machine.

As a distinction: In Bug 1700200, the running System-Monitor shows a significant impact in the CPU-graph. This bug does not raise actual CPU-Load as plotted in System-Monitor. Also I didn't notice the fan spinning up, as it does in 1700200.

This System is:
Operating System: Kubuntu 20.10
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2
Kernel Version: 5.8.0-53-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4700MQ CPU @ 2.40GHz
Memory: 15.6 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

This looks like a graphics issue. But it's not clear to me if WebRender is enabled or not. Holger, could you please check in about:support what the Graphics table contains, and if doable paste it here?

The Gecko profile shows long composite times (~1s each). Maybe related to bug 1692828, but that's on MacOS.

Comment 2

[Holger]

Attachment: ff_about_support_89b15.json

Spoiler: Compositing WebRender

See full text of about:support in attachment.

Comment 3

[Holger]

Now, that I read the other bug 1692828 ... on startup of FF-dev there is the notification complaining, not to be the standard-browser - well, it is extracted in my Downloads - not, what I want as a standard :D

The notification of available updates on the other hand, did not really seem to bother me performance-wise, though it kept following me around with multiple FF windows open all the time.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Spoiler: Compositing WebRender

Thanks! That indeed makes it a graphics bug. Maybe you can record a new profile with the Firefox Graphics preset? thanks.

Comment 5

[Timothy Nikkel (:tnikkel)]

Does the problem still happen if you set gfx.webrender.force-disable to true in about:config?

Comment 6

[Holger]

record a new profile with the Firefox Graphics preset

What? How do I change this?

gfx.webrender.force-disable to true

done

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+2]]

(In reply to Holger from comment #6)

record a new profile with the Firefox Graphics preset

What? How do I change this?

There is a little arrow right next to the toolbar button. Click on it, and then select the wanted preset from the drop down.

Comment 8

[Jim Mathies [:jimm]]

If you can provide that Graphics profile that would be great. Looks similar to Bug 1709763 - Menus show a delay of 4-5 seconds on mouse input (Wayland/WebRnender?).

Comment 9

[Holger]

Hello Jim,

This is the Graphics-profile, that I took after the update 89b15 -> 90b1
(first half I waited and then I wildly play with the menus)
https://share.firefox.dev/3uAVLNK

But I think, it didn't trigger the error, because resizing the window feels OK, no significant lag. Will have to wait for beta 2 for another shot ...

This is WebRenderer, but not Wayland, as far as I can tell: https://unix.stackexchange.com/questions/202891/how-to-know-whether-wayland-or-x11-is-being-used
holger 22:46:54 1 7 2006 ~
$ loginctl show-session 3 -p Type
Type=x11
holger 22:47:00 OK 8 2007 ~
$ loginctl
SESSION UID USER SEAT TTY
3 1000 holger seat0

1 sessions listed.
holger 22:47:11 OK 9 2008 ~
$ loginctl show-session 3 -p Type
Type=x11
holger 22:47:16 OK 10 2009 ~
$ echo $XDG_SESSION_TYPE
x11

Comment 10

[Holger]

Attachment: Screenshot_20210603_221131.png

Update to 90b2 is reporting itself as 90b1 in about:support and help / about

• I reenabled and saw the question for dev-edition not being the default browser
• In case they are interacting: I didn't restart since last time bug 1700200, but woke from suspend2ram with lo CPU
• I dismissed the notification popup and instead updated via help / about

This still did not trigger the error. Only thing I can think of now, is the flag:
gfx.webrender.force-disable actually I set:
gfx.webrender.force-disabled (with an additional D at the end) to true
shall I set it to false again and see, if this brings back the error?

Comment 11

[Jim Mathies [:jimm]]

(In reply to Holger from comment #10)

Created attachment 9225065 [details]
Screenshot_20210603_221131.png

Update to 90b2 is reporting itself as 90b1 in about:support and help / about

• I reenabled and saw the question for dev-edition not being the default browser
• In case they are interacting: I didn't restart since last time bug 1700200, but woke from suspend2ram with lo CPU
• I dismissed the notification popup and instead updated via help / about

This still did not trigger the error. Only thing I can think of now, is the flag:
gfx.webrender.force-disable actually I set:
gfx.webrender.force-disabled (with an additional D at the end) to true
shall I set it to false again and see, if this brings back the error?

The old layers system is going away so webrender is all we're concerned about. If things are performing well there that good to hear.

In the profile composition and rendering don't stand out. Composition times are tight. You do have a lot of activity going on in your webextension process, but not enough to cause any major lag AFAICT. If you see this again please try to collect a profile. With the delays you were seeing that would definitely standout in a profile.

Comment 12

[Holger]

Haven't seen this in a while ... So I try to close ...