Why does Chrome and Edge browsers glitch and freeze?

English Applications
22

Update. Now both Chrome and Edge are glitching and freezing. Any other ideas on how to fix this??

23

Well … I forget … did you create a new user account, login as that user, then test for glitchiness ??

Anyway, I see a couple options.

  1. Switch to use X11 vs Wayland, because you wrote no glitchiness with X11
  2. Install the apps using the dedicated repos or rpms … vs using Flatpaks.

No doubt #1 is something you’ll avoid, since you mentioned everything else runs fine with Wayland

So, #2 is probably the option. But of course, that could result with glitches , though doubtful

Have you ever tried installing the versions that are not Flatpak? If yes, any issues?

1 Like
24

Very good suggestion. Soon as I get back from work I’ll look for the non-flatpak versions.

25

Examples

## add repo chrome

zypper ar http://dl.google.com/linux/chrome/rpm/stable/x86_64 Google-Chrome

wget https://dl.google.com/linux/linux_signing_key.pub

rpm --import linux_signing_key.pub

zypper ref -f

## install
zypper in google-chrome-stable

====== brave browser

https://brave.com/linux/

zypper addrepo https://brave-browser-rpm-release.s3.brave.com/brave-browser.repo

zypper install brave-browser

==== edge dev

## Setup
rpm --import https://packages.microsoft.com/keys/microsoft.asc

zypper ar https://packages.microsoft.com/yumrepos/edge microsoft-edge-dev

## Install
zypper refresh
zypper install microsoft-edge-dev

## Setup edge beta

rpm --import https://packages.microsoft.com/keys/microsoft.asc

zypper ar https://packages.microsoft.com/yumrepos/edge microsoft-edge-beta

## Install
zypper refresh
zypper install microsoft-edge-beta
1 Like
26

Adding repos without auto refresh flag will lead earlier or later to issues (package version not found). So please try to remember to always use the auto refresh flag -f. Also importing the signing certificate can be done as one liner.

Add repo

sudo zypper ar -f http://dl.google.com/linux/chromed/rpm/stable/x86_64 google-chrome

Import signing key:

sudo rpm -import https://dl-ssl.google.com/linux/linux_signing_key.pub

Install Chrome:

sudo zypper in google-chrome-stable
1 Like
27

Could someone provide the commands to install Edge Stable? Thanks.

28 
sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc

sudo zypper ar -f https://packages.microsoft.com/yumrepos/edge microsoft-edge

sudo zypper install microsoft-edge-stable
1 Like
29

Now installed. Seems to be working ok.

30

Now installed. Seems to be working OK.

31

The good thing about adding those browser repos, is when a “zypper dup” is executed, zypper will also check for any browser updates, and if applicable, will install the update(s).

1 Like
32

Maybe clear the GPU cache:

find ~/.config/Chrome/ -depth -type d -name GPUCache -exec rm -rf {} \;
1 Like
33

Only if you added the auto refresh flag. A „zypper dup“ only refrehes the metadata of repos with enabled auto refresh flag. This was really often discussed in the forum.

Also the man pages explains clearly, that new repos ( like you showed in your example), have auto-refresh disabled and need an explicit
zypper ref prior update. This can be avoided by proper repo management like adding the auto refresh flag.

1 Like
34

I’d say, on most browser installations for folks, that will not work.
Why? Because your suggested start path is assumed to work for everyone.
Personally, on all our systems, “~/.config/Chrome/” does not exist.

And it will definitely not work for anyone who has installed the FlatPak version of Chrome (etc) browsers. Let me show where the GPUCache is found in my home base path. I’ve made comments in the output.

And notice, for the Flatpaks for Chrome and Edge, the GPUCache is NOT even in the “.config” path (but located down in ~/.var). I ran the find command in the base of my home-dir:

One other thing to note … there are other apps besides browsers that have a GPUCache sub-dir path (which is also shown below)

user@machine:~> cd
user@machine:~> find . -name GPUCache -ls

## brave native-installed browsers

./.config/BraveSoftware/Brave-Browser/Default/GPUCache
./.config/BraveSoftware/Brave-Browser-Beta/Default/GPUCache

## chrome native-installed browsers

./.config/google-chrome/Default/GPUCache
./.config/google-chrome-beta/Default/GPUCache
./.config/google-chrome-beta/Default/Storage/ext/xxyyzz/def/GPUCache
./.config/google-chrome-unstable/Default/GPUCache
./.config/google-chrome-unstable/Default/Storage/ext/xxyyzz/def/GPUCache

## chromium native-installed browsers

./.config/chromium/Default/GPUCache

## chrome FlatPak browser

./.var/app/com.google.Chrome/config/google-chrome/Default/GPUCache
./.var/app/com.google.Chrome/config/google-chrome/Default/Storage/ext/xxyyzz/def/GPUCache

## edge FlatPak browser

./.var/app/com.microsoft.Edge/config/microsoft-edge/Default/GPUCache
./.var/app/com.microsoft.Edge/config/microsoft-edge/Default/Storage/ext/xxyyzz/def/GPUCache

## these are NOT browser-related GPUCache

./.local/share/openSUSE/org.opensuse.opensuse_welcome/QtWebEngine/Default/GPUCache
./.local/share/konqueror/QtWebEngine/Default/GPUCache
./.local/share/digikam/QtWebEngine/Default/GPUCache
./.local/share/kontact/QtWebEngine/Default/GPUCache
1 Like
35

Looks like it’s good for me to run “sudo zypper refresh” each time before I run “sudo zypper dup”. That sound right? That will make sure the Packman repo, the Chrome repo and the Edge repo will always be up to date?

Can the two commands be combined on one line?

36

Simply add the auto refresh flag for this repos via “YaST-> Software repositories”. That is the most easiest solution and you only need to perform zypper dup onwards (as already explained above). No additional zypper ref needed than…

1 Like
37

OK, thanks for the tip. Looks like all my repos are set to autorefresh. See here: openSUSE Paste

Looks like I’m all set?