Bug 106700 - Chromium choppy due to vsync errors when running on XWayland
Summary: Chromium choppy due to vsync errors when running on XWayland
Alias: None
Product: Wayland
Classification: Unclassified
Component: XWayland (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Wayland bug list
QA Contact: Xorg Project Team
Depends on:
Reported: 2018-05-28 18:26 UTC by sosic.martin
Modified: 2019-05-10 15:53 UTC (History)
9 users (show)

See Also:
i915 platform:
i915 features:


Description sosic.martin 2018-05-28 18:26:29 UTC
When running Chromium over Gnome on Wayland (which uses XWayland for it), experience is choppy / stuttering. OS is Archlinux.

Checking chrome://gpu shows errors related to vsync:
[1687:1687:0525/081927.341246:ERROR:sync_control_vsync_provider.cc(141)] : Calculated bogus refresh interval=0.810638 s, last_timebase_=44680100 bogo-microseconds, timebase=46301376 bogo-microseconds, last_media_stream_counter_=302, media_stream_counter=304

Google Chrome behaves exactly the same way.

Machine: Dell XPS 15, 9560, 4K internal screen, 32GB RAM, 1TB SSD, discrete Nvidia GPU, integrated Intel Video card.
  Kernel: 4.16.9-1-ARCH, options: acpi_rev_override=1 acpi_osi=! acpi_osi='Windows 2015'. I need first one for basic stuff to work, next two I need for bbswitch to not freeze everything on boot.
  Bootloader: GRUB, and I also have intel-ucode.
  Video: I have bumblebee + bbswitch, they work fine. Drivers are `nvidia` (when bbswitch is on) and i915 otherwise. I dont have xf86-intel-video installed. I do have nouveau still installed, but it is not visible in dmesg and since `nvidia` package is blacklisting it. During tests above I confirmed that they are running on integrated intel video card.
    gnome: 3.28.2-1
    google-chrome: 66.0.3359.181-1
    chromium: same as google-chrome
    nvidia: 396.24-3
    wayland: 1.15.0-1
    bumblebee: 3.2.1-17
    bbswitch: 0.8-135

If I run Chromium on Gnome over Xorg, it works fine.

Other (Archilnux) users have also confirmed that they are having this problem, on KDE specifically.

Known fixes:
- Downgrading xorg-server from 1.20 to 1.19 fixes the issue.
- Alternatively, setting `--disable-gpu-driver-bug-workarounds` flag for Chromium fixes the issue.

Additionally, Atom and other Electron based app also seems to be suffering from the same problem, although it has not been that explored and should probably be additionally confirmed.

More details regarding the error on the original post about it: https://bbs.archlinux.org/viewtopic.php?id=237383 .
Comment 1 sosic.martin 2018-05-28 18:33:11 UTC
I forgot to mention versions of xorg and xwayland:
xorg-server-xwayland: 1.20.0-2
xorg-server: 1.20.0-2
Comment 2 Mathias Anselmann 2018-08-17 12:17:23 UTC
It's also the case with xorg 1.20.1.
Very nasty bug, chromium / chrome is more or less unusable for me with wayland sessions. Had to go back to a xorg session.
Comment 3 Sergi Granell 2018-09-07 19:54:08 UTC
I have the same problem.
Kernel: 4.18.5-arch1-1-ARCH
OpenGL version string: 3.0 Mesa 18.1.7
xorg-server-xwayland 1.20.1-1
Google Chrome Version 69.0.3497.81 (Official Build) (64-bit)

Adding --disable-gpu-driver-bug-workarounds fixes it but spams "ERROR:gl_surface_presentation_helper.cc(115)] GetVSyncParametersIfAvailable() failed!".
Comment 4 Sergi Granell 2018-12-10 18:15:04 UTC
Now I'm running:
Intel i7-8750H (UHD Graphics 630 (Coffeelake 3x8 GT2))
Kernel: 4.19.4-arch1-1-ARCH
Mesa 18.2.6
xorg-server-xwayland 1.20.3-1
GNOME Shell 3.30.2
Google Chrome 71.0.3578.80 (Official Build) (64-bit)

And the issue seems to be fixed (--disable-gpu-driver-bug-workarounds no longer needed).
Comment 5 Niklas Haas 2019-01-29 14:26:39 UTC
Oops, I didn't realize tracking for Wayland/XWayland had moved over to gitlab.

Reopened as https://gitlab.freedesktop.org/xorg/xserver/issues/631
Comment 6 Niklas Haas 2019-01-29 14:28:09 UTC
Wrong tab, sorry for the noise.
Comment 7 GitLab Migration User 2019-05-10 15:53:54 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/721.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.