Open korbav opened 3 years ago
@jc-kynesim I'm seeing this as well. Is --enable-gpu-memory-buffer-compositor-resources
something that makes sense to use and should be supported?
As a first reaction: "not a clue". Chrome has more switches than it is possible to list never mind test - in general you get switches enabled by default that google actually supports for the platform you are on. I'll grant that that switch looks superficially attractive but I'm guessing it has hit a wall of "not implemented" somewhere. I'll have a quick look for the next version as at least some of what is appears to be failing there should probably work, google seems to still be doing a certain amount of catchup in their switch to ozone.
I tried the same with the official v97 snap and haven't had any luck there either. I'll leave it open for now, but it sounds like something we won't end up supporting.
In my dev v98 build on current bullseye either that flag works or it does nothing - it doesn't produce errors. But I've still got some things to look at in terms of GL buffer allocation.
I just noticed that as soon as the
--enable-gpu-memory-buffer-compositor-resources
switch is enabled to launch chromium-browser within an X11 session opened without the sudo privileges, the browser won't render anything except fuzzy black squares on a white background. (As soon as the switch is removed, everything works).I've been able to detect some errors messages that led me to think that this has to be related to the GPU not being used at all in that case.
And