chromium freezes gnome if hardware acceleration is activated in browser setttings (U20.04) Intel HD-Grafik 4400

Bug #2039701 reported by Affenputtel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu 20.04 have to deaktivate hardware acceleration in browser stetting in order to prevent delay and crash of chromium broswer and chrome browser. Was able to reboot with strg+alt+F(x) sudo reboot

found line /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed in syslog when crash happened. Let me to this via gürgelschnüffel:

vainfo
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.6.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell - 2.4.0
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple : VAEntrypointVLD
      VAProfileMPEG2Simple : VAEntrypointEncSlice
      VAProfileMPEG2Main : VAEntrypointVLD
      VAProfileMPEG2Main : VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main : VAEntrypointVLD
      VAProfileH264Main : VAEntrypointEncSlice
      VAProfileH264High : VAEntrypointVLD
      VAProfileH264High : VAEntrypointEncSlice
      VAProfileH264MultiviewHigh : VAEntrypointVLD
      VAProfileH264MultiviewHigh : VAEntrypointEncSlice
      VAProfileH264StereoHigh : VAEntrypointVLD
      VAProfileH264StereoHigh : VAEntrypointEncSlice
      VAProfileVC1Simple : VAEntrypointVLD
      VAProfileVC1Main : VAEntrypointVLD
      VAProfileVC1Advanced : VAEntrypointVLD
      VAProfileNone : VAEntrypointVideoProc
      VAProfileJPEGBaseline : VAEntrypointVLD

Affenputtel (hoskdlsk2)
summary: chromium freezes gnome if hardware acceleration is activated in browser
- setttings
+ setttingsv (20.04)
Affenputtel (hoskdlsk2)
summary: chromium freezes gnome if hardware acceleration is activated in browser
- setttingsv (20.04)
+ setttingsv (20.04) i3-4170 i apu
Affenputtel (hoskdlsk2)
summary: chromium freezes gnome if hardware acceleration is activated in browser
- setttingsv (20.04) i3-4170 i apu
+ setttingsv (20.04) Intel HD-Grafik 4400
summary: chromium freezes gnome if hardware acceleration is activated in browser
- setttingsv (20.04) Intel HD-Grafik 4400
+ setttings (U20.04) Intel HD-Grafik 4400
Revision history for this message
Nathan Teodosio (nteodosio) wrote :

> Was able to reboot with strg+alt+F(x) sudo reboot

Once this happens again, can you please collect dmesg and journalctl (some hundreds of lines are probably enough) before rebooting?

Instead of launching Chromium normally, use

  chromium --enable-logging=stderr > chromium.log 2>&1

Also:

  snap connections chromium
  snap info chromium

> via gürgelschnüffel:
>
> vainfo

First the most important question: What is Gürgelschnüffel?

Now, running vainfo in your host system doesn't help much, because Chromium is supposed to use the driver provided by the (not ideally named, I know) Gnome snap, /snap/gnome-42-2204/current/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so.

Revision history for this message
Nathan Teodosio (nteodosio) wrote :

Another possible hint to collect: Does this happen both in X11 and Wayland?

Revision history for this message
Affenputtel (hoskdlsk2) wrote (last edit ):

If hardware acceleration is turned on chromium crashes almost every time i start it, i will never do it again. If its turned off then it is ok. But it crashed anyway when the indicator applet was showing incoming mail last time. Yes the legendary Gürgelschnüffel is german cacography for googlesearch.

Files in Attachment:

chromiumlog is crash with hardware acceleration on

dmesg 1 is with hardware acceleration on

dmesg 2 maybe contains something with crash before from hardware acceleration off

Ubuntu 20.04.6 LTS
X11
gnome version 3.36.8

Now the gnome crashed as i resized a yt window, a had also strange glitches in the player if i maximized it but its rather rare. see picture in next post. but gnome didnt crash, but when gnome crashes completely then also sometimes likewise glichtes appear on the screen. Maybe the apu is damaged? Or 13y old Power Supply 300 Watt Bequiet . But i dont think so.

Revision history for this message
Affenputtel (hoskdlsk2) wrote :
Revision history for this message
Nathan Teodosio (nteodosio) wrote (last edit ):

OK, hang on, the title claims that Gnome crashes if hardware acceleration is activated. You are now reporting problems also with it deactivated, right?

> If its turned off then it is ok. But it crashed anyway when the indicator applet was showing incoming mail last time.

With hardware acceleration turned off?

> Now the gnome crashed as i resized a yt window, a had also strange glitches in the player if i maximized it but its rather rare.

With hardware acceleration turned off?

You apparently have an extension installed, is the problem reproducible with it uninstalled? Did you try reproducing the problem in a non-snapped version of the browser?

For my future reference: The video issues here described are not related to hardware accelerated video decoding, as the user is in stable channel and, at the time of writing, only beta and edge channels have hardware accelerated video decoding.

Revision history for this message
Affenputtel (hoskdlsk2) wrote (last edit ):

Hi there, thank you for your help. Yes i also have problems with deactivated hardware accel. But they are very seldom.

1. yes turned off

2 yes also off

If i turn hardware accel on, chromium almost every time crashes gnome if i start it its a pain in the b because i have to reboot every single time. The Youtube Player Glitch is now absent for longer, as i update my chromium regularly i think it was a problem of a past version maybe or its only now and then, i cant confirm.

I have an older non snappend version of the browser, i can start and end it without problems with HARDWARE ACCEL ON [Version 115.0.5769.0 (Entwickler-Build) (64-Bit)].
I deleted my profile folder: /home/user/snap/chromium and then the same problem, it crashes gnome and hardware accel is on then. No problem with the Extentions so.

Plus i logged out and logged in again with wayland, and in wayland the chromium also crashed. In wayland it started a few times without problems and crashed then. In wayland stange things happened, in the task obive there was a gjfs button or so and i clicked it and tehre was a number df8s87s7s6s66s7 and view details, it opened software center, and one time the launcher menu down left didnt work. Then i started ubuntu again without wayland and verything was normal again (X11).

Revision history for this message
Affenputtel (hoskdlsk2) wrote (last edit ):

I forgot to mention that there are other programs that cause the same crash, maybe they use chromium code? For example:
https://flathub.org/apps/io.github.Bavarder.Bavarder

There were other programs, but can only remember that super tux cart has a problem alike. Only if in the game in graphics settings " lightscattering or ambientocclusion " is activated https://github.com/supertuxkart/stk-code/issues/4904

Revision history for this message
Affenputtel (hoskdlsk2) wrote :

There is a new thing, i figured out that the system freezes only approximately in the first hour of use, if i let it run the system rarely freezes or not at all, i cant remember exactly.

Revision history for this message
Affenputtel (hoskdlsk2) wrote (last edit ):

I think its because its a flatpak and snap, some flatpaks and snaps crash the desktop. Flatseal for instance.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.