Chromium tabs freeze with two windows on Wayland (Xwayland)

Bug #1906792 reported by Alberto Donato
52
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Mutter
New
Unknown
mutter (Ubuntu)
Confirmed
Medium
Unassigned
xwayland (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Original description:
When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow.

This usually happens with specific pages open, like youtube, mattermost, google drive.

Minimizing one of the two windows makes the other work fine.

The issues does not happen if both windows are on the same workspace.

I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session.

---

Updates:
As for #1916458 this behaviour may happen also on the same workspace and with Google Chrome

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.1-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
Uname: Linux 5.8.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Fri Dec 4 09:39:08 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-10-18 (46 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Alberto Donato (ack) wrote :
affects: gnome-shell (Ubuntu) → mutter (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mutter (Ubuntu):
status: New → Confirmed
summary: Chromium tabs freeze with two windows on different workspaces on Wayland
+ (Xwayland)
Changed in xorg-server (Ubuntu):
status: New → Confirmed
summary: - Chromium tabs freeze with two windows on different workspaces on Wayland
- (Xwayland)
+ Chromium tabs freeze with two windows on Wayland (Xwayland)
Changed in mutter (Ubuntu):
importance: Undecided → Medium
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: added: performance
fcole90 (fcole90)
description: updated
fcole90 (fcole90)
description: updated
Revision history for this message
fcole90 (fcole90) wrote :

I recently noted that if I put a window over the other, the bug appears, but if I put one next to the other, then everything works fine and smooth

Revision history for this message
fcole90 (fcole90) wrote :

Since few days, I'm experiencing the same behaviour under X. Shall I open a separate report for that?

tags: added: focal
removed: groovy
Revision history for this message
Dimitris Moraitidis (dimisjim) wrote :

Any news regarding this?

This pretty much blocks me from switching to Wayland in Ubuntu 22.04

affects: xorg-server (Ubuntu) → xwayland (Ubuntu)
Changed in mutter:
status: Unknown → New
Revision history for this message
hami hamza (hamzapped) wrote :

So this issue was reported in 2020 and is still an issue in 2023...

Using KDE on manjaro linux.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If you experience the issue on Manjaro then please subscribe to https://gitlab.gnome.org/GNOME/mutter/-/issues/1563 instead...

Although there is also this menu bug at the moment which is a little bit similar: https://bugs.chromium.org/p/chromium/issues/detail?id=1427954

Revision history for this message
Mauro Gaspari (ilvipero) wrote :

I have the exact same issue as described by original report. Two windows of the browser on different workspaces, only happens when I use Wayland session. I collected more data on this:

Release: Ubuntu Noble Numbat 24.04 and Ubuntu Mantic Minotaur 23.10
Hardware: Dell Inspiron-16-Plus-7620, i7-12700H, 32GB RAM.
Browsers tested: Vivaldi (deb), Brave (deb), Brave (snap), Chromium (snap)

As suggested by @vanvugt , I switched one browser setting, and it immediately solved the issue for me on all browsers affected.

chrome://flags/#ozone-platform-hint
Changed from default (always use x11), to auto (try wayland first, fallback to x11).

It is quite easy to check that the setting is applied, by running this on the browser: chrome://gpu/
Searching the text for "ozone" I can see the following:

--ozone-platform-hint=auto
--ozone-platform=wayland

I hope this helps. Please let me know if further testing is required.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.