[Bug 1149308] New: Cromium instable: windows do not react after a while and GotoMeeting consumes extremely high processor power
http://bugzilla.suse.com/show_bug.cgi?id=1149308 Bug ID: 1149308 Summary: Cromium instable: windows do not react after a while and GotoMeeting consumes extremely high processor power Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: knut.trepte@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Cromium Version 76.0.3809.100 (openSUSE Build) (64-bit) - Windows sometimes freeze and do not react any more and can not be moved. - GotoMeeting consumes high processor power expecially when video is used. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1149308
Knut Trepte
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c2
Lubos Kocman
http://bugzilla.suse.com/show_bug.cgi?id=1149308
Lubos Kocman
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c3
Lubos Kocman
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c4
Marco Varlese
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c5
Vincent Untz
It isn't just hardware with NVidia being affected... I have a laptop with Intel integrated GPU and have the exact same issue.
Same here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c6
--- Comment #6 from Tomáš Chvátal
(In reply to Marco Varlese from comment #4)
It isn't just hardware with NVidia being affected... I have a laptop with Intel integrated GPU and have the exact same issue.
Same here.
Then provide the traces, the gpu thread can crash, but otherwise the vaapi offloading should work. See chrome://gpu page. The only way when it should not really work well is when you are on wayland... Anyhow this is how it looks on my lappy and it offloads the rendering: Graphics Feature Status for Hardware GPU Canvas: Hardware accelerated Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Out-of-process Rasterization: Disabled Hardware Protected Video Decode: Hardware accelerated Rasterization: Software only. Hardware acceleration disabled Skia Renderer: Disabled Video Decode: Hardware accelerated Viz Display Compositor: Enabled Viz Hit-test Surface Layer: Enabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated This is how it will look on unsupported system: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only. Hardware acceleration disabled Flash Stage3D: Software only. Hardware acceleration disabled Flash Stage3D Baseline profile: Software only. Hardware acceleration disabled Compositing: Software only. Hardware acceleration disabled Multiple Raster Threads: Enabled Out-of-process Rasterization: Disabled Hardware Protected Video Decode: Disabled Rasterization: Software only. Hardware acceleration disabled Skia Renderer: Disabled Video Decode: Software only. Hardware acceleration disabled Viz Display Compositor: Enabled Viz Hit-test Surface Layer: Enabled Vulkan: Disabled WebGL: Software only, hardware acceleration unavailable WebGL2: Software only, hardware acceleration unavailable Note that there is nothing much that can be done by us as chromium will not merge any fixes for the gpu acceleration on linux, they only focus on windows/android/chromebook in this regard... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c7
--- Comment #7 from Marco Varlese
(In reply to Vincent Untz from comment #5)
(In reply to Marco Varlese from comment #4)
It isn't just hardware with NVidia being affected... I have a laptop with Intel integrated GPU and have the exact same issue.
Same here.
Then provide the traces, the gpu thread can crash, but otherwise the vaapi offloading should work.
See chrome://gpu page.
The only way when it should not really work well is when you are on wayland...
Anyhow this is how it looks on my lappy and it offloads the rendering:
Graphics Feature Status for Hardware GPU Canvas: Hardware accelerated Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Out-of-process Rasterization: Disabled Hardware Protected Video Decode: Hardware accelerated Rasterization: Software only. Hardware acceleration disabled Skia Renderer: Disabled Video Decode: Hardware accelerated Viz Display Compositor: Enabled Viz Hit-test Surface Layer: Enabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated
This is how it will look on unsupported system:
Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only. Hardware acceleration disabled Flash Stage3D: Software only. Hardware acceleration disabled Flash Stage3D Baseline profile: Software only. Hardware acceleration disabled Compositing: Software only. Hardware acceleration disabled Multiple Raster Threads: Enabled Out-of-process Rasterization: Disabled Hardware Protected Video Decode: Disabled Rasterization: Software only. Hardware acceleration disabled Skia Renderer: Disabled Video Decode: Software only. Hardware acceleration disabled Viz Display Compositor: Enabled Viz Hit-test Surface Layer: Enabled Vulkan: Disabled WebGL: Software only, hardware acceleration unavailable WebGL2: Software only, hardware acceleration unavailable
Note that there is nothing much that can be done by us as chromium will not merge any fixes for the gpu acceleration on linux, they only focus on windows/android/chromebook in this regard...
It does show as "unsupported system". Tomas, what I tried to point out is that it does not only affect NVidia hardware but also non-NVidia hardware. I do appreciate that there is not much you can do to fix the issue either. I only wanted to make sure the broader issue was being covered as it is not specific to a GPU vendor only. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c8
--- Comment #8 from Tomáš Chvátal
It does show as "unsupported system".
Tomas, what I tried to point out is that it does not only affect NVidia hardware but also non-NVidia hardware.
That is weird, so even if you play some 4k video on youtube it is offloaded on CPU? Could you try chrome://flags/ and enable feature "Override software rendering list"? Basically with anything except the nvidia you should be "all green" and it should offload the stuff. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c9
--- Comment #9 from Marco Varlese
(In reply to Marco Varlese from comment #7)
It does show as "unsupported system".
Tomas, what I tried to point out is that it does not only affect NVidia hardware but also non-NVidia hardware.
That is weird, so even if you play some 4k video on youtube it is offloaded on CPU?
Could you try chrome://flags/ and enable feature "Override software rendering list"?
Basically with anything except the nvidia you should be "all green" and it should offload the stuff.
Done. I am going to have my next GTM call just tomorrow morning so will try to run it by Chromium and see what happens. Would you mind sharing any command I should run to capture anything important when the issue present itself? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1149308
Matthias Eckermann
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c11
--- Comment #11 from Vincent Untz
Anyhow this is how it looks on my lappy and it offloads the rendering:
Graphics Feature Status for Hardware GPU Canvas: Hardware accelerated Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Out-of-process Rasterization: Disabled Hardware Protected Video Decode: Hardware accelerated Rasterization: Software only. Hardware acceleration disabled Skia Renderer: Disabled Video Decode: Hardware accelerated Viz Display Compositor: Enabled Viz Hit-test Surface Layer: Enabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated
Looks the same here except for: Hardware Protected Video Decode: Unavailable I do have "Video Decode: Hardware accelerated", though. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c12
--- Comment #12 from Tomáš Chvátal
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c13
--- Comment #13 from Marco Varlese
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c14
--- Comment #14 from Dirk Mueller
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c15
Michael Matz
http://bugzilla.suse.com/show_bug.cgi?id=1149308
http://bugzilla.suse.com/show_bug.cgi?id=1149308#c16
--- Comment #16 from Marco Varlese
FWIW, I have no hardware accell in chromium, but no stuckiness or overly high CPU load on my system. It's Intel hardware only, and chrome://gpu says everything software only. I have shared the camera and show it nearly full screen and my CPU load as at 100%, i.e. only one CPU out of the eight I have.
So, when GTM becomes laggy it's _not_ the missing GPU hardware accelleration in itself that causes it. But it might of course lower the stuckiness factor for those that exhibit it.
(FWIW, openSUSE 12.3, kernel 3.7.10-1.16, chrome 72.0.3626.96)
Indeed something I also concluded early in the morning re GPU acceleration involvement. See my comment #13 and attached image. mvarlese@localhost:~> cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20200110" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20200110" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20200110" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" LOGO="distributor-logo" mvarlese@localhost:~> uname -r 5.4.7-1-default Chromium Version 79.0.3945.117 (openSUSE Build) (64-bit) -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com