Why does Chrome and Edge browsers glitch and freeze?

I’m using TW on an AMD Ryzen 7 laptop with Gnome and Wayland and 40GB RAM. Often when I use the Edge and Chrome browsers they’ll continually glitch and freeze up for a few seconds. Once they start doing this, I have to restart my laptop to fix this problem. The problem does not stay fixed after a reboot.

This problem has been going on for about 15 months. Anyone have ideas as to what causes these problems? Both browsers are installed as flatpaks. Could flatpak be the root cause? I update all my flatpaks once per week.

Firefox never has this problem. I think my Firefox is installed as RPM.

  1. 15 months?! Haven’t troubleshooted till now?
  2. You’ll need to perform one or more troubleshooting procedures.
  3. Doubtful issue is “because Flatpaks”

I have no issues here (though we’re on Leap 15.6) with performance of Flatpak apps.

Heck, there are distros that rely solely on the use of Flatpak apps.

Are the glitches ONLY with certain websites? Or only videos? Only with specific content?

Create a new user account - log into it. Test apps with new user

Login with X11 vs Wayland. Test performance of apps.

1 Like

@invalid_user_name likely issues with the AMD gpu… are you running Mesa from packman?

1 Like

I don’t know. How can I tell or find out? Is there a command I can run?

TBH, I don’t know what Mesa or packman are.

Glitches seem to happen with any website. And as far as I can see only Chrome browser and Edge browser have this problem. No other apps affected.

@invalid_user_name zypper if Mesa | grep -E "Repository :|Version :"

1 Like

When I logged out of Wayland and logged into X, the Chrome and Edge browsers behaved normally with no glitching. When I logged out of X and back into Wayland, the Edge browser was glitching and the Chrome browser had no glitching.

advait@localhost:~> zypper if Mesa | grep -E "Repository     :|Version        :"
Repository     : Main Repository (OSS)
Version        : 25.0.3-412.1
advait@localhost:~> 

Helpful?

@invalid_user_name I would suggest you add the Packman Extras repo and switch to the Packman version of Mesa.

zypper ar -f -g -n "Packman Extras (Mesa)" https://ftp.fau.de/packman/suse/openSUSE_Tumbleweed/Extra/ repo-mesa

zypper -vvv dup -r repo-mesa

Trust the key always, then select Solution 1 for the respective packages listed to switch, reboot and test…

1 Like

OK, I’ll try your suggestion. Thanks. Just in case, I’ll make sure and take a snapshot before running the command.

OK, I followed the instructions and so far Edge and Chrome seem to be operating normally. Cool. I’ll keep this ticket open for a day or 2 just to see if the problem returns.

1 Like

The glitches and freezing came back to Edge but Chrome is still OK.

@invalid_user_name Isn’t edge an electron app? Might need some environment variables…

1 Like

Edge is based on the Chromium engine - a fork of Chromium source.

Microsoft Teams was initially an Electron app.

1 Like

@invalid_user_name can you show the output from inxi -SGaz

1 Like

Interesting feedback. That’s why we don’t use Wayland. For our systems, there’s always glitches here and there, and not for browsers, but the whole UI (we use KDE Plasma on Leap) experience.

Question about your Edge … do you have the “Dev” release installed? Or the Standard release?

1 Like

I don’t know. How can I tell? Is there a command that can tell me?

(Google says it’s not an electron app.)

I have the “Official build”. See image below.
000----------------

000---------------

AFAICT, my Wayland Gnome UI/UX is pretty close to perfect with zero issues, except for the periodic glitching of flatpak Chrome and flatpak Edge. All my other apps work flawlessly in terms of UI/UX, AFAICT.

I’ve been using my existing setup for about 2.5 years.

Update, Edge is still glitching and freezing. Chrome behaving normally.