Summary: | www-client/chromium, www-client/google-chrome-113.0.5672.126: Broken on AMD GPUs after media-libs/mesa-23.1.1 update | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Piotr Karbowski (RETIRED) <slashbeast> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gentoo, herrtimson, kangie, silvio.gerli |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bbs.archlinux.org/viewtopic.php?id=285507 | ||
See Also: |
https://bugs.archlinux.org/task/78403 https://bugzilla.redhat.com/show_bug.cgi?id=2193335 https://bugs.chromium.org/p/chromium/issues/detail?id=1442633 https://bugzilla.opensuse.org/show_bug.cgi?id=1211983 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Runtime output of starting google-chrome-stable |
From the reports on Archlinux forum it seems to affect only AMD GPUs users Some suggested workarounds: 1) add --disable-gpu-driver-bug-workarounds to launch arguments 2) rm -rf ~/.config/chromium/Default/GPUCache if running chromium 3) rm -rf ~/.config/google-chrome/Default/GPUCache if running Chrome Arch bug report: https://bugs.archlinux.org/task/78403 Upstream chromium bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=1442633 Fedora bug report: https://bugzilla.redhat.com/show_bug.cgi?id=2193335 I think I'm seeing a similar bug after an update this morning, but with media-libs/mesa-23.0.3-r1:0 and Chrome Version 114.0.5735.106 (Official Build) (64-bit) [on an AMD GPU]. This morning's update was: 1686579369: Started emerge on: Jun 12, 2023 09:16:09 1686579407: >>> emerge (1 of 11) dev-util/strace-6.3 to / 1686579455: >>> emerge (2 of 11) dev-libs/nspr-4.35-r2 to / 1686579470: >>> emerge (3 of 11) dev-python/fonttools-4.39.4 to / 1686579500: >>> emerge (4 of 11) dev-python/weasyprint-59.0 to / 1686579507: >>> emerge (5 of 11) net-print/cups-2.4.4 to / 1686579541: >>> emerge (6 of 11) sys-devel/llvm-15.0.7-r3 to / 1686582174: >>> emerge (7 of 11) app-portage/gemato-20.4 to / 1686582180: >>> emerge (8 of 11) media-libs/gstreamer-1.20.5 to / 1686582206: >>> emerge (9 of 11) dev-db/unixODBC-2.3.11 to / 1686582239: >>> emerge (10 of 11) media-libs/gst-plugins-base-1.20.5 to / 1686582282: >>> emerge (11 of 11) www-client/firefox-bin-114.0.1 to / I see scrambled window content, the same error messages spewing on the console window where chrome was launched, and the --disable-gpu-driver-bug-workarounds option seems to be an effective work-around. I suspect it's the llvm update that was the problem, but I haven't tried backing that out. (In reply to Grant Edwards from comment #3) If you're hitting this bug, you can try purging the GPUCache dir as well. > If you're hitting this bug, you can try purging the GPUCache dir as well.
Yep, that also fixes it.
(In reply to Grant Edwards from comment #5) > > If you're hitting this bug, you can try purging the GPUCache dir as well. > > Yep, that also fixes it. It works for me too. The same thing just happened to me with media-libs/mesa-23.0.3-r1 and www-client/chromium-114.0.5735.198. Chromium was working fine last night, after some updates (and full restart) this morning I get artifacts like missing text and parts of graphics. However it's rather new install - and emerge.log says that neither mesa nor chromium were updated - so it's possible another thing/combination is causing this? Meanwhile www-client/google-chrome-114.0.5735.198 is not affected. But it's likely it's GPU cache was empty since this is few days old install, and I didn't install/start google-chrome until I got garbage in chromium. Workaround `rm -rf ~/.config/chromium/Default/GPUCache` fixed the problem. This was fixed upstream for 121, no older versions in tree: - https://issues.chromium.org/issues/40267041#comment106 |
Created attachment 862914 [details] Runtime output of starting google-chrome-stable After media-libs/mesa-23.1.1 update the www-client/google-chrome-113.0.5672.126 and what seems to be all Chromium downstreams like www-client/opera-99.0.4788.31 stopped working in a sense that all webpages were flickering, missing content, all kind of weird artifacts. To recovery from it one needs to either start with '--disable-gpu-driver-bug-workarounds' or remove GPUCache directory out of Chrome (Chromium, Opera) profile directories. After the GPUCache is purged the browsers no longer breaks.