1754979 - gpu cpu usage firefox horizon openstack

Status: UNCONFIRMED

(Core :: Graphics, defect)

Description

[Rossen]

Attachment: firefox_unusual_gpu_usage.png

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

Steps to reproduce:

I'm using the web interface for Openstack, which is called Horizon.

1. Navigate between certain pages, that's it

As far as I can tell, it not caused by addons, and I can reproduce on Linux too. I don't see anything particular about the page that stands out either. I'm not sure how to get more information to help narrow down the cause.

Actual results:

Firefox CPU usage increases, and GPU usage on a couple of Windows process also increases. It stays like that until I close the tab. The usage remains high even if I navigate to complete different site.

There is nothing interactive on the pages that trigger the condition

Expected results:

Short spike when loading the page, but settling back to idle

Comment 1

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

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Jamie Nicol [:jnicol] (on leave until 21st October)]

Hi Rossen, thank you for the bug report. Is there a publicly accessible URL that we can use to test?

Could you please try capturing a performance profile by going to profiler.firefox.com and following the instructions to install the addon. Select the "Firefox Graphics" settings preset, go to the slow page then start the profiler and wait for around 10 seconds, then capture the profile. This should open the profile a new tab, and in the top right corner there will be an option to upload the profile. Please select that then post the URL here.

If you need any help with that please let me know!

Comment 3

[Rossen]

Hi Jamie, thanks for the information. I cannot provide a public URL. Here is the profile https://share.firefox.dev/3HO8ML7 Around 2-4s is when I triggered the condition.

Comment 4

[Jamie Nicol [:jnicol] (on leave until 21st October)]

Thanks Rossen. Could you also please navigate to about:support, click on "copy text to clipboard" and attach the copied text as an attachment to this bug?

Comment 5

[Rossen]

Attachment: firefox-support.txt

Comment 6

[Jamie Nicol [:jnicol] (on leave until 21st October)]

Thanks for that. I can see that we're detecting your display link adapter as GPU#1, and your nvidia card as GPU#2. Because we don't know what to do with the display link adapter we disable hardware acceleration. The software renderer is expected to be slightly slower but it does seem to be particularly struggling with this page, but it's hard to tell why.

I'm afraid I'm unfamiliar with how display link is supposed to work. Do you know whether you get hardware acceleration in other applications? If you have chrome or edge installed, could you attach the contents of chrome://gpu or edge://gpu? If you unplug the display link adapter then launch firefox is the performance better?

Comment 7

[Rossen]

Attachment: chrome-gpu.txt

Comment 8

[Jamie Nicol [:jnicol] (on leave until 21st October)]

Jeff, can you see anything interesting in this chrome://gpu? (From the machine with the display link adapter we talked about the other day)

I can see that they also detect the display link adapter, and the nvidia one, and they additionally see an intel one that we don't. And it looks like they get acceleration?

Comment 9

[Rossen]

The setup I have is a Lenovo X1 connected to USB-C Dock that is connected to an external high refresh rate monitor. I've not notice problems on other sides, including ones with dynamic content or video. I was able to reproduce this issue on same X1 laptop running Ubuntu 20.04. The site as far as I can tell from the dev tools is not doing anything crazy. All of that leads me to think that the issue is somewhere in Firefox. The firefox process also has increased CPU usage (12-15% on the picture), so the cause may not be graphics.

The increased usage stays there, on page that is not doing anything, until the tab closed. Navigating away form the site in the same tab, doesn't make a difference. Only closing the tab. If I reopen the site on new tab, or restore the closed, tab the page loads normally, and firefox idles at 0-1% with tiny or no gpu usage.

Comment 10

[Jeff Muizelaar [:jrmuizel]]

Yeah, I think we probably need to improve our GPU detection to better do that right thing in this configuration. Rossen, can you try setting gfx.webrender.all=true, restarting and see if it makes a difference? (Perhaps post you about:support from that configuration as well)

Comment 11

[Rossen]

No difference in the output of about:support with gfx.webrender.all=true. Using the laptop monitor only with the dock connected also shows GPU#1 as displaylink. Only with dock disconnected shows as Intel iGPU.

Original issue reproduced without the dock connected o the laptop: https://share.firefox.dev/3p1LzxO