You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enables Display Compositor to use a new gpu thread.
When enabled, chrome uses 2 gpu threads instead of 1. Display compositor uses new dr-dc gpu thread and all other clients (raster, webgl, video) continues using the gpu main thread. – Mac, Windows, Linux, ChromeOS, Android, Fuchsia, Lacros
#enable-drdc
Then if you go to chrome://gpu
Graphics Feature Status
=======================
* Canvas: Hardware accelerated
* Canvas out-of-process rasterization: Enabled
* Direct Rendering Display Compositor: Disabled
* Compositing: Hardware accelerated
* Multiple Raster Threads: Enabled
* OpenGL: Enabled
* Rasterization: Hardware accelerated on all pages
* Raw Draw: Disabled
* Skia Graphite: Disabled
* Video Decode: Hardware accelerated
* Video Encode: Hardware accelerated
* Vulkan: Disabled
* WebGL: Hardware accelerated
* WebGL2: Unavailable
* WebGPU: Hardware accelerated
The Direct Rendering Display Compositor is still Disabled.
Backgrounds
chrome://flags settings
Problems
As the title says.
If you try to enable
chrome://flags/#enable-drdc
Then if you go to
chrome://gpu
The
Direct Rendering Display Compositor
is stillDisabled
.Some said in the link below that it's exclusive to android, but I don't really know.
https://bbs.archlinux.org/viewtopic.php?id=285762
Additional info from chrome://gpu for my specific system
P.S. --disable-gpu-driver-bug-workarounds doesn't work
The text was updated successfully, but these errors were encountered: