-
You never mentioned “what you are doing” when there is a “chrome failure”.
Does Chrome crash when starting it?
Does crash only happen when you visit a specific website?
Does it “hang” (unresponsive) instead of an actual crash?
Something else? -
Unfortunately, the error output is not informative (appears to be in an [endless] loop). Might see more informative info by starting Chrome at the command line.
-
More than one reinstall is over-doing it. Same for reboots. Reboots can be avoided by simply logging out of your user account and log in again.
-
What happens if you login using “Plasma X11” instead of “Plasma wayland”? Does it still crash?
Another quick troubleshooting step is to: create a new user account (that you’ve never used before), log out of your normal user account, log in as the new user, fire up Chrome … still experience the crash?
I used to run TW a long time ago - I’m now on Leap.
I always experienced an issue running Chrome on TW, after doing a “zypper dup”: Chrome would either not start, or website rendering would be corrupted. (and not just me, but many folks using Chrome-based browsers).
The issue was that Chrome’s GPUCache sub-directory would somehow get corrupted (always after a “dup”) … the fix was easy - simply delete the content of GPUCache sub-dir. I ended up creating a script to clear it out. Since moving to Leap, I’ve never had a GPUCache issue for all 3 versions of Chrome and Brave.
Here’s one old post where I describe the issue and how to fix it … not saying the GPUCache issue is your issue, but worth checking out - only takes a couple of minutes to test. Lot’s of folks on TW w/Chrome have experienced this GPUCache issue.