Arch Linux

surefire

Member

Registered: 2015-12-16

Posts: 11

Re: Chromium is intermittently very choppy

There is another solution I used and it works

--disable-gpu-driver-bug-workarounds

Since most workarounds are too old and have long been solved.
But it is better to highlight specific workarounds for shutdown than all at once.

Is there a way for electron-based app to set this? Thanks.

Yes, of course, but I don't know the only common way. Each electron-based application has its own implementation of the launcher.

Martinsos

Member

From: Croatia

Registered: 2015-08-27

Posts: 61

Re: Chromium is intermittently very choppy

Since Chromium is working fine when run directly on xorg server, and it does not work fine when run on xwayland, I am guessing that the real problem is in xwayland? Maybe multi buffering update in xorg-server is causing problems with xwayland and they have to fix it there? I will consider posting a bug to xwayland then.

@surefire: Thanks for the temporary solution! Where would I set that flag if I am running Chromium on xwayland?

@schmidtbag: Thanks for the tip! However I am not using KDE, I have been using XFCE in the past and now Gnome (due to it's HiDPI support). For my main editor I am actually using Emacs (mostly for C/C++, Python). I use Atom only for Javascript development, because support in Emacs is still not good enough for JSX unfortunately, I guess because not so many JS developers are using Emacs.

Maybe there is a bug when passing data in xwayland? But it seems that downgrade xserver fix the bug, not xwayland...

It is hard to say exactly if problem is in xorg server or in xwayland, since Chromium is working fine when run directly on Xorg. It could be that xorg server updated and part of xwayland is not handling that update correctly. Or maybe xorg server introduced bug in a part of code that is being used by xwayland. Anyway, maybe best to start from xwayland guys and see what they say.

schmidtbag

Member

From: NH, USA

Registered: 2011-02-08

Posts: 344

Re: Chromium is intermittently very choppy

First of all, thanks surefire for the tip - it worked great.

It's tough to know what's really the culprit here.  It makes sense how xserver is the problem, because only that needed to be downgraded in order to fix the problem.  On the other hand, I really think the multi-buffering support implemented in xwayland has something to do with it, since the errors Chrome(ium) gave were specific to vsync.
However...
Since multi-buffering is a new implementation in xwayland, perhaps version 1.20 can't utilize it unless xserver supports/allows it.

In other words, I really think xwayland is the problem here, but, it's only a problem if you're using the same version of xserver.

Martinsos

Member

From: Croatia

Registered: 2015-08-27

Posts: 61

Re: Chromium is intermittently very choppy

I filed a bug on Wayland's Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106700 .
I can also confirm that using --disable-gpu-driver-bug-workarounds fixes the problem! Thanks everybody.

stecklars

Member

Registered: 2013-10-29

Posts: 8

Re: Chromium is intermittently very choppy

I am affected by this as well. Doing --disable-gpu-driver-bug-workarounds works, but if I run chrome via terminal / look into chrome://gpu, it is spammed with the message
"ERROR:gl_surface_presentation_helper.cc(115)] GetVSyncParametersIfAvailable() failed!"

Cabbage_c

Member

Registered: 2016-06-24

Posts: 8

Re: Chromium is intermittently very choppy

Thank you very much for the tip, surefire! I've experienced this problem since early this year, but never succeeded to locate it

There is another solution I used and it works

--disable-gpu-driver-bug-workarounds

Since most workarounds are too old and have long been solved.
But it is better to highlight specific workarounds for shutdown than all at once.

abmantis

Member

Registered: 2015-01-08

Posts: 13

Re: Chromium is intermittently very choppy

I am affected by this as well. Doing --disable-gpu-driver-bug-workarounds works, but if I run chrome via terminal / look into chrome://gpu, it is spammed with the message
"ERROR:gl_surface_presentation_helper.cc(115)] GetVSyncParametersIfAvailable() failed!"

Same here, and it is probably wasting CPU doing that. Any workaround?

angordeyev

Member

Registered: 2019-12-22

Posts: 1

Re: Chromium is intermittently very choppy

"--disable-gpu-driver-bug-workarounds" fix artifacts when you resize a window dragging the window border but new artifacts appear when you maximize or minimize a window on Gnome Wayland.

amaro

Member

From: 5.11.1-1-ck-ivybridge, xfce

Registered: 2014-05-09

Posts: 366

Re: Chromium is intermittently very choppy

chromium is not only choppy it often freezes the system and I need to reboot using the power button cause neither the keyboard nor touchpad works

running in terminal

$ chromium
[50905:50905:1229/054405.874689:ERROR:gpu_channel_manager.cc(450)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.

chrome://gpu/ output

Graphics Feature Status
Canvas: Software only. Hardware acceleration disabled
Flash: Software only. Hardware acceleration disabled
Flash Stage3D: Software only. Hardware acceleration disabled
Flash Stage3D Baseline profile: Software only. Hardware acceleration disabled
Compositing: Software only. Hardware acceleration disabled
Multiple Raster Threads: Disabled
Out-of-process Rasterization: Disabled
Hardware Protected Video Decode: Disabled
Rasterization: Software only. Hardware acceleration disabled
Skia Renderer: Disabled
Video Decode: Software only. Hardware acceleration disabled
Viz Display Compositor: Enabled
Viz Hit-test Surface Layer: Enabled
Vulkan: Disabled
WebGL: Disabled
WebGL2: Disabled
Problems Detected
GPU process was unable to boot: GPU access is disabled in chrome://settings.
Disabled Features: all
Raster is using a single thread.
Disabled Features: multiple_raster_threads
Version Information
Data exported	2019-12-29T03:44:24.719Z
Chrome version	Chrome/79.0.3945.79
Operating system	Linux 5.4.2-1-ck-ivybridge
Software rendering list URL	https://chromium.googlesource.com/chromium/src/+/29f75ce3f42b007bd80361b0dfcfee3a13ff90b8/gpu/config/software_rendering_list.json
Driver bug list URL	https://chromium.googlesource.com/chromium/src/+/29f75ce3f42b007bd80361b0dfcfee3a13ff90b8/gpu/config/gpu_driver_bug_list.json
ANGLE commit id	unknown hash
2D graphics backend	Skia/79 64f0af0f6548f7b8c45e7e3b2630e34deb04c1aa
Command Line	/usr/lib/chromium/chromium --ppapi-flash-version=32.0.0.303 --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --cipher-suite-blacklist=0x0001,0x0002,0x0004,0x0005,0x0017,0x0018,0xc002,0xc007,0xc00c,0xc011,0xc016,0xff80,0xff81,0xff82,0xff83,0x0033,0x0039,0x0067,0x006b,0x009e --disable-gpu-vsync=gpu --disable-gpu-driver-bug-workarounds --password-store=detect --disable-sync-preferences --disk-cache-dir=/tmp/cache --disable-reading-from-canvas --force-device-scale-factor=1 --flag-switches-begin --disable-threaded-scrolling --disable-smooth-scrolling --enable-features=LazyFrameLoading,LazyImageLoading,OverscrollHistoryNavigation --flag-switches-end --disable-webrtc-apm-in-audio-service
Driver Information
Initialization time	0
In-process GPU	false
Passthrough Command Decoder	false
Sandboxed	true
GPU0	VENDOR= 0x0000, DEVICE=0x0000
Optimus	false
AMD switchable	false
Driver vendor	
Driver version	
GPU CUDA compute capability major version	0
Pixel shader version	
Vertex shader version	
Max. MSAA samples	
Machine model name	
Machine model version	
GL_VENDOR	Disabled
GL_RENDERER	Disabled
GL_VERSION	Disabled
GL_EXTENSIONS	
Disabled Extensions	
Disabled WebGL Extensions	
Window system binding vendor	
Window system binding version	
Window system binding extensions	
Window manager	Xfwm4
XDG_CURRENT_DESKTOP	XFCE
Compositing manager	No
Direct rendering version	unknown
Reset notification strategy	0x0000
GPU process crash count	0
System visual ID	0
RGBA visual ID	0
gfx::BufferFormats supported for allocation and texturing	R_8: not supported, R_16: not supported, RG_88: not supported, BGR_565: not supported, RGBA_4444: not supported, RGBX_8888: not supported, RGBA_8888: not supported, BGRX_8888: not supported, BGRX_1010102: not supported, RGBX_1010102: not supported, BGRA_8888: not supported, RGBA_F16: not supported, YVU_420: not supported, YUV_420_BIPLANAR: not supported, P010: not supported
Compositor Information
Tile Update Mode	One-copy
Partial Raster	Enabled
GpuMemoryBuffers Status
R_8	Software only
R_16	Software only
RG_88	Software only
BGR_565	Software only
RGBA_4444	Software only
RGBX_8888	Software only
RGBA_8888	Software only
BGRX_8888	Software only
BGRX_1010102	Software only
RGBX_1010102	Software only
BGRA_8888	Software only
RGBA_F16	Software only
YVU_420	Software only
YUV_420_BIPLANAR	Software only
P010	Software only
Display(s) Information
Info	Display[21571318625337410] bounds=[0,0 1600x900], workarea=[0,35 1600x865], scale=1, external.
Color space information	{primaries:INVALID, transfer:INVALID, matrix:INVALID, range:INVALID}
SDR white level in nits	80
Bits per color component	8
Bits per pixel	24
Refresh Rate in Hz	59
Video Acceleration Information
Driver Information for Hardware GPU
Initialization time	0
In-process GPU	false
Passthrough Command Decoder	false
Sandboxed	true
GPU0	VENDOR= 0x0000, DEVICE=0x0000
Optimus	false
AMD switchable	false
Driver vendor	
Driver version	
GPU CUDA compute capability major version	0
Pixel shader version	
Vertex shader version	
Max. MSAA samples	
Machine model name	
Machine model version	
GL_VENDOR	Disabled
GL_RENDERER	Disabled
GL_VERSION	Disabled
GL_EXTENSIONS	
Disabled Extensions	
Disabled WebGL Extensions	
Window system binding vendor	
Window system binding version	
Window system binding extensions	
Window manager	Xfwm4
XDG_CURRENT_DESKTOP	XFCE
Compositing manager	No
Direct rendering version	unknown
Reset notification strategy	0x0000
GPU process crash count	0
System visual ID	0
RGBA visual ID	0
gfx::BufferFormats supported for allocation and texturing	R_8: not supported, R_16: not supported, RG_88: not supported, BGR_565: not supported, RGBA_4444: not supported, RGBX_8888: not supported, RGBA_8888: not supported, BGRX_8888: not supported, BGRX_1010102: not supported, RGBX_1010102: not supported, BGRA_8888: not supported, RGBA_F16: not supported, YVU_420: not supported, YUV_420_BIPLANAR: not supported, P010: not supported
Graphics Feature Status for Hardware GPU
Canvas: Software only. Hardware acceleration disabled
Flash: Software only. Hardware acceleration disabled
Flash Stage3D: Software only. Hardware acceleration disabled
Flash Stage3D Baseline profile: Software only. Hardware acceleration disabled
Compositing: Software only. Hardware acceleration disabled
Multiple Raster Threads: Disabled
Out-of-process Rasterization: Disabled
Hardware Protected Video Decode: Disabled
Rasterization: Software only. Hardware acceleration disabled
Skia Renderer: Disabled
Video Decode: Software only. Hardware acceleration disabled
Viz Display Compositor: Enabled
Viz Hit-test Surface Layer: Enabled
Vulkan: Disabled
WebGL: Disabled
WebGL2: Disabled
Problems Detected for Hardware GPU
GPU process was unable to boot: GPU access is disabled in chrome://settings.
Disabled Features: all
Raster is using a single thread.
Disabled Features: multiple_raster_threads
Log Messages
[50905:50905:1229/054405.874689:ERROR:gpu_channel_manager.cc(450)] : ContextResult::kFatalFailure: Failed to create shared context for virtualization.

nano ~/.config/chromium-flags.conf

--cipher-suite-blacklist=0x0001,0x0002,0x0004,0x0005,0x0017,0x0018,0xc002,0xc007,0xc00c,0xc011,0xc016,0xff80,0xff81,0xff82,0xff83,0x0033,0x0039,0x0067,0x006b,0x009e
--disable-gpu-vsync=gpu
--disable-gpu-driver-bug-workarounds
--password-store=detect
--disable-sync-preferences
--disk-cache-dir=/tmp/cache
--disable-reading-from-canvas
--force-device-scale-factor=1

p.s. For the record, just checked the xorg-server downgrade options, 1.19 is not currently available

# downgrade xorg-server
Available packages:

-   1)  xorg-server    1.20.4  1  x86_64  (remote)
-   2)  xorg-server    1.20.5  1  x86_64  (remote)
-   3)  xorg-server    1.20.5  2  x86_64  (remote)
    4)  xorg-server    1.20.5  3  x86_64  (remote)
-   5)  xorg-server    1.20.5  4  x86_64  (remote)
-   6)  xorg-server    1.20.5  4  x86_64  (local)
-   7)  xorg-server    1.20.6  1  x86_64  (remote)
-   8)  xorg-server    1.20.6  1  x86_64  (local)
+   9)  xorg-server    1.20.6  2  x86_64  (remote)
+  10)  xorg-server    1.20.6  2  x86_64  (local)

RadioGnome1971

Member

From: At home

Registered: 2013-12-27

Posts: 12

Re: Chromium is intermittently very choppy

Since a few weeks I have exactly the above issues with Chromium and VisualStudio Code, running on XWayland / Gnome. Adding the --disable-gpu-driver-bug-workarounds did not do anything.

As this is totally not my territory to investigate this, is there any new light on the matter? If this is a common problem, I expected the forum to be flooded with hopeless users..

I quite lament seeing my 10 years old Arch install (on VM-Ware) rendered useless for my python / iot tinkering.

Kind regards,

Martin

liewkj

Member

Registered: 2019-07-08

Posts: 210

Re: Chromium is intermittently very choppy

I don't know about VisualStudio Code, but for Chromium check if you included flags that uses EGL instead of desktop GL. Bug was already filed upstream.
https://bugs.chromium.org/p/chromium/is … id=1041228
The workaround is to temporary downgrade xwayland to 1.19.7.
https://bbs.archlinux.org/viewtopic.php … 5#p1884305
Ubuntu 18.04LTS has explicitly retained xwayland in this version, so perhaps someone was already aware of the potential issue. Google/Chromium test engineering does not seem to deploy verification on Wayland. They are still mainly on Ubuntu 16.04 that has no Wayland at all.

Last edited by liewkj (2020-03-20 22:29:05)

RadioGnome1971

Member

From: At home

Registered: 2013-12-27

Posts: 12

Re: Chromium is intermittently very choppy

I don't know about VisualStudio Code, but for Chromium check if you included flags that uses EGL instead of desktop GL.

Thanks for lending me a hand on this journey!! Learning something again.

With an educated guess from the source-code I added

--use-gl=egl

to my ~/.config/chromium-flags.conf

Now I was able to use Chromium in a hunt for the VS-Code solution.

Off topic
Found a way to disable GPU acceleration for VisualStudioCode, which seems to do the trick.

In the Preferences: Configure Runtime Arguments
one can easily enable the setting

"disable-hardware-acceleration": true,