Google Chrome locking up KDE/Xorg

English Applications
1

Not sure if this is a chrome, KDE, Xorg, or SUSE bug but it just popped up after a recent update. Chrome and Suse were updated at the same time.

Chrome is now 121.0.6167.85

> cat /etc/os-release 
NAME="openSUSE Tumbleweed"
# VERSION="20240126"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20240126"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20240126"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"

When I launch chrome my desktop freezes, I can move the mouse around and the pointer moves but I cannot interact with anything, and theres a box outline where chrome should be. The desktop will stay like this until I restart or kill the chrome process. Once the chrome process is killed desktop is responsive and everything works fine. To kill the process I have to switch to a virtual terminal and kill the PID.

Launching chrome from the command line the only feedback I get is the following:

[19388:19388:0129/105937.100559:ERROR:atom_cache.cc(224)] Add _ICC_PROFILE_1 to kAtomsToCache

I can get chrome to launch properly through the command line by launching into an incognito window. When I do this I can then create a new regular window and restore my regular sessions without issue. Im kind of at a loss on this one with how to further track things down to get a proper fix to it. Everything seems to work after I launch in incognito, but launching it normally causes the issue. Anyone else experience something similar or does anyone have pointers on how to approach trying to resolve this.

2

An easy test:
Create a new regular user account.
Log out of your normal acct.
Login as the new user

Test Chrome. Any difference? Same behavior, or locks up too?
.
.
Sidenote: may need the delete Chrome’s GPUCache sub-dir

3

No need for a complete new user account as the incognito mode works. Only a fresh Google Chrome profile is required as first test.

Normaly the Google Chrome user profile is located under /.config/google-chrome/Default. You can rename this directory or move it temporarily away and try to start Google Chrome normaly.

4

I’d rather just try the removal of GPUCache first :slight_smile:

5

Removing the GPUCache directories from all the profile dirs seemed to resolve the issue. Thanks for the pointer.

1 Like
6

Shockingly enough, it’s an easy fix, and sadly enough, we see this issue crop up many times over the course of a year. Seems it’s related to updates to “Mesa” packages. When you see that in a" zypper dup", be prepared to delete :slight_smile:

7

Im kind of surprised I havent run into it before, though Firefox is my main browser. Guess I finally got “lucky” and hit this issue.

8

Yea, Firefox is not based on Chrome, so isn’t affected.
It’s browsers like Chrome, Chromium, Vivaldi, Opera, Brave, (cough) Edge, (among others), that are affected because they inherit from the base Chrome.

9

So yeah its either the latest chrome/mesa/nvidia or something else seems to have really kicked this into overdrive. While chrome launches I get frequent lockups like above when closing open chrome windows. Seems like I can replicate the behavior consistently when having a virtual console popup window launched from proxmox. When I close the opened virtual console window my dekstop (minus the cursor) fails to update anything until I go and kill the chrome process from a terminal.

I have removed all my profiles, launched chrome like it were a new install and can consistently cause this behavior.

10

I simply run this when my Chrome* based browsers have rendering issues (as my regular user):

$   find ~/ -type d -name GPUCache | grep ".config"  -exec rm -rf {} +