Chromium or Chromium based browser issues

[tinycorelinux]

The main problem is as shown in the figure: address bar, menu bar, right-click menu can not be
displayed normally, are black, nothing can be seen.

[Juanito]

I'd guess that some local customisation you've done is causing this - see attached

[tinycorelinux]

I'd guess that some local customisation you've done is causing this - see attached

Yes, the last two screenshots you see show the effect after I did some configuration on the browser, while the first two screenshots show the effect without any configuration on the browser, which is simply unusable.

my guess is that my graphics card doesn't support Chrome's GPU acceleration mode. As far as I know, Chrome has removed most graphics support, and only the graphics card models listed in Chrome are fully GPU accelerated.

However, GPU acceleration is very important for me in Linux, especially in Chrome. I found that with GPU acceleration enabled, web pages opened and loaded so fast that I could hardly believe my eyes. Moreover, the CPU load was so low that the CPU indicator light almost went out.

[Juanito]

We both get the same message:

Code: [Select]

InitializeSandbox() called with multiple threads in process gpu-process..so I'm not sure that the gpu is the problem.

[tinycorelinux]

..so I'm not sure that the gpu is the problem.

hmm...Does your browser work properly with GPU acceleration enabled?

[tinycorelinux]

I find that almost everyone on the web has only one answer to chrome GPU acceleration problems, and that's to tell you to turn it off...

If it can't be solved, I have to give up. You have tried your best.
Thank you , Juanito.

[vinceASPECT]

hello,

well judging by what you say, in chromium & derivatives at least, the GPU acceleration (if possible) makes a huge difference to browsing.

Is this type of difference (good performance)  reflected in other browsers where they see the machines GPU correctly?.... like say FF........?

or what browsers realy shine in this area?.....MsoftEdge?

thx

V

i was messing around with browsers  on an old Msoft machine here...... (winXP sp2).
The latest version of a certain browser just would not run, .........so after rooting around in their forum, there was a final trick to patch an sp3 version of "kernnel32.dll" file into the OS instead of it's sp2 version. 

I did the patch and the browser works fine on a 20 year old laptop....it surfs all todays modern web sites pretty good.........youtube etc....facebook...
(Goanna engine) kmeleon76.

i also had to patch the browser itself with 2 DLL files for doing html5 viideo and they are lean-trimnmed DLL's for sp2....(it works)

i will run this same browser on the same machine under TCL and WINE .......and it should work fine.

This machine only has an SSE cpu chip and only supports FF 45 from TCL.....which isn't that great of a browser on performance here......................compared to KMeleon under wine and the same hardware

[vinceASPECT]

....could there be a flag that you need to set in the  CHromium browser?

chrome://flags  (into the address bar)

There are lots of flags to set on Chromium concerning GPU's

thx

V

[Juanito]

Here's what I see from chrome://gpu/

Code: [Select]

Graphics Feature Status
Canvas: Hardware accelerated
CheckerImaging: Enabled
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only. Hardware acceleration disabled
Video Decode: Unavailable
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
...
Problems Detected
Accelerated video decode is unavailable on Linux: 137247
Disabled Features: accelerated_video_decode
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
...
Chrome version Chrome/66.0.3343.0
Operating system Linux 5.4.3-tinycore64
GPU0 VENDOR = 0x8086, DEVICE= 0x0a16 *ACTIVE*
...
GL_RENDERER Mesa DRI Intel(R) Haswell Mobile

..apparently chromium-browser needs to be patched for va-api (accelerated video decode) to work.

[tinycorelinux]

..apparently chromium-browser needs to be patched for va-api (accelerated video decode) to work.

Are you saying that this may be related to a problem I have?

[Juanito]

I don't know - you'd need intel graphics hardware for intel-vaapi-driver to work anyway - what do you get for chrome://gpu?

[Juanito]

I get this in firefox:

Code: [Select]

GPU #1
Active: Yes
Description: Mesa DRI Intel(R) Haswell Mobile x86/MMX/SSE2
Vendor ID: 0x8086
Device ID: 0x0a16
Driver Vendor: mesa/i965
Driver Version: 19.2.3.0
RAM: 1536
..which suggests the problem is with chromium-browser

[tinycorelinux]

which suggests the problem is with chromium-browser

All right -_-||

[vinceASPECT]

It seems you are well on the way to nailing down the issue concerning Chromium browser on Linux....
(at least)

so is it saying that accelerated video decode is a problem in ANY graphics chips set ...e.g. (amd or intel set)?

i wonder *how* one is suppossed to actually patch chromium--on--Linux to get accelerated video decode...... then?

wonder if accelerated vid decode (chromium) is okay on other platforms?( no names mentioned)?
---
---

unrelated stuff below

------------------------------------
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
-----------------------------------

those lines above could mean that dev's just don't find it acceptable regarding MSAA but users could enable the flags if they wished....just  to see and perhaps gain some ground.  (about:flags )written into address bar

thx

V

[tinycorelinux]

Hi vinceASPECT

wonder if accelerated vid decode (chromium) is okay on other platforms?( no names mentioned)?

We have a lot of Chrome based browsers in Mainland China, but they only support Windows platforms. As far as I know, these browsers turn off GPU acceleration by default, so I don't know if they will have the same problem at first, but they do perform very well.

I feel the browser's performance is not only the GPU, because behind the GPU is video card drive and graphics library, both on different operating systems have different implementation,different performance, such as in Windows is the main use of graphics library Direct3D, and under Linux using OPENGL, the difference is largely determines the rendering performance of the browser.

I may not be able to say this much, but I just want to say that browser performance is not a one-way decision. There are many factors, and I only try various ways to improve my performance based on the resources I have, such as GPU acceleration, which we are discussing here.