brave://gpu I see five graphics feature items as disabled or set for software only:
* Native GpuMemoryBuffers: Software only. Hardware acceleration disabled * Out-of-process Rasterization: Disabled * Skia Deferred Display List: Disabled * Skia Renderer: Disabled * Surface Control: Disabled
The goals is for all items to be hardware based/enabled.
The “problems detected” portion of the report describes:
* Native GpuMemoryBuffers have been disabled, either via about:flags or command line. * Disabled Features: native_gpu_memory_buffers * Skia renderer is not used by default. * Disabled Features: skia_renderer * Skia deferred display list is not used by default. * Disabled Features: skia_deferred_display_list
Notice the “GpuMemoryBuffers have been disabled either via about:flags or command line”. If I look in brave://flags there is no entry for this. Search for ‘memory’ and you’ll not find a flag related to GpuMemoryBuffers. But if you look over here: https://peter.sh/experiments/chromium-command-line-switches/ (last updated 2019) and search for ‘memory’ you’ll find a lot of flags that Chrome (which Brave is based off of) exposes to users. So where did they go in Brave, please, b/c I’d like to make some switches.
Additionally, I’m looking for the
--cipher-suite-blacklist flag which isn’t picked up if I run
So then to return to the question:
- where is the list of accepted flags that Brave supports?
- how can I correct the above five disabled/software-only GPU features (Skia etc) including GpuMemoryBuffers ?
- Can you also link me to your (or Google) documentation that describes/explains (verbosely) these items? Or the docs that describe the flags they’re controlled by?
Uh-Oh - so it looks like my other issue that I didn’t detail initially regarding Widevinecdm is not just because I’m doing something stupid (brave://components doesn’t list it!)… You actually haven’t gotten round to adding this into the build yet, have you: http\s://github.com/brave/brave-browser/issues/413 although people have been requesting it for years…
So that’s a lot of media content I won’t be able to view… You know, I really didn’t want to whine but I’m finding more reasons just to revert back to Chromium, particularly as the Arch Linux AUR has this: https://aur.archlinux.org/packages/chromium-vaapi/ which looks like it will answer my issues that about hardware acceleration & skia that this post has been about. Then there’s the missing flags (others I’m after that aren’t detailed in this post) that seem to be missing in too…
As if that’s not enough, the other issue I have is that despite this bug Brave shield UI bug having been solved, the fix still hasn’t made it into the Brave package for Arch-Linux users https://aur.archlinux.org/packages/brave-bin/
…Was really looking forward to decoupling from Chromium/Chrome.