On my Raspberry Pi4 I have a new strange problem with Chromium. Things don’t change if I open a window in incognito mode.
And again, things don’t change if I use another Chromium-based browser: for example, I tried Brave, installed by Flatpak.
However, I have not experienced any problem with Firefox (which, however, has always been much slower than the other browsers).
It seems to be some rendering bug related to some graphics library, although Flatpak by itself should provide some independence from the default operating system libraries.
I also tried disabling hardware acceleration in the settings but the result did not change in Brave, while Chromium works much better (maybe it’s ok, I have to verify it carefully).
I attach two screenshots.
Am I the only one with this problem?
In Chrome, open a new tab and type chrome://gpu in the address bar, then scroll to the bottom of the page. Are there any errors there?
This is log:
* [6631:6631:0924/173126.101703:WARNING:sandbox_linux.cc(393)] : InitializeSandbox() called with multiple threads in process gpu-process.
* [6631:6631:0924/173126.180494:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.182577:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.184527:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.186041:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.187416:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.189204:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.190803:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.205902:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.207796:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.209212:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.210716:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.212337:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.213791:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173126.215308:ERROR:gbm_wrapper.cc(253)] : Failed to export buffer to dma_buf: File o directory non esistente (2)
* [6631:6631:0924/173152.213143:ERROR:gl_surface_presentation_helper.cc(260)] : GetVSyncParametersIfAvailable() failed for 1 times!
* [6631:6631:0924/173152.224510:ERROR:gl_surface_presentation_helper.cc(260)] : GetVSyncParametersIfAvailable() failed for 2 times!
* [6631:6631:0924/173154.749422:ERROR:gl_surface_presentation_helper.cc(260)] : GetVSyncParametersIfAvailable() failed for 3 times!
(“File o directory non esistente” means “File or directory does not exist”)
> cd ~/.config/chromium/Default/GPUCache
> ls -alp
totale 388
drwx------ 2 mr mr 4096 24 set 17.31 ./
drwx------ 38 mr mr 4096 24 set 17.35 …/
-rw------- 1 mr mr 45056 24 set 17.32 data_0
-rw------- 1 mr mr 270336 24 set 17.36 data_1
-rw------- 1 mr mr 1056768 24 set 17.32 data_2
-rw------- 1 mr mr 8192 24 set 17.31 data_3
-rw------- 1 mr mr 262512 24 set 17.32 index
deleting these files did not resolve the problem.
Maybe the only solution is to disable hardware acceleration, but one/two weeks ago this was not necessary.
After doing some testing, I confirm that disabling hardware acceleration solves the problem in Chromium and also in Brave installed via Flatpak. Alternatively, I should use Firefox, but that is a choice I would not want to make, because it is definitely slower on my Raspberry PI4. Anyway, disabling hardware acceleration was not necessary a few weeks ago, so probably some update introduced a bug.
Yes, this is probably some mesa or gpu driver update.
Is hardware accel working on Firefox? You keep mentioning that it’s slower than the other two browsers, so is it using software rendering always? AFAIR there were no big speed differences between FF/Chrome on PIs I’ve used.
In Firefox settings, the option is “Use recommended performance settings” and it’s switched on at the moment.
In my own experience, in x86 architectures Firefox and Chrome/Chromium have comparable performance (although, having enough RAM, Chrome has a higher speed in my opinion).
But on my Raspberry PI4 there is no match: Chromium is much faster. Firefox is almost unusable for shopping on Amazon or using Google Documents, whereas Chromium is usable. I can state this not only for EndeavourOS: before switching to this distribution, I tried others, such as Ubuntu MATE and Manjaro: in all these distributions Firefox was too slow.
