Image rendering and hardware acceleration issues

[tanquang]

Since version v5.2.1168.76 to v5.2.1168.83, I discovered a problem; when the browser renders images, it often appears to have a blank space (both above and below the image). Only when switching to another tab or minimizing the browser and then reopening will it render the blank part of the image. Here is the screen recording video I recorded:



And also on both of these versions, when checking in chrome://gpu, I see the value of Video Decode and Video Encode are both Hardware accelerated. Here are the 2 report files on these 2 versions: v5.2.1168.76 chrome gpu.txt and v5.2.1168.83 chrome gpu.txt.

But when watching videos (like on YouTube), it will decode using the CPU instead of the GPU.

When viewing in Task Manager - Cent Browser, most tasks like "Browser", "GPU Process", and the YouTube tab all use GPU memory. But it seems that because it doesn't use a GPU, the CPU is used a lot.

P/s: Version v5.2.1168.83 still does not fix the problem of the browser always using a small amount of CPU when in idle state that I reported before.

[Admini]

Not sure if it's related to this command line:
--disable-zero-copy
Or you could try changing the value of this flag:
chrome://flags/#use-angle

[tanquang]

Not sure if it's related to this command line:
--disable-zero-copy
Or you could try changing the value of this flag:
chrome://flags/#use-angle

Most of the flags are used since Chrome 109; many of them are gone, but since they don't affect anything, I won't change them. And since there is no official documentation of the flags that CentBrowser supports, I don't think it matters either.

Details about the --disable-zero-copy flag can be found here and here.

Since it has the potential to crash the browser, and it also seems to be disabled by default, I think it's unlikely to be the cause.

[Admini]

Most of the flags are used since Chrome 109; many of them are gone, but since they don't affect anything, I won't change them. And since there is no official documentation of the flags that CentBrowser supports, I don't think it matters either.

Details about the --disable-zero-copy flag can be found here and here.

Since it has the potential to crash the browser, and it also seems to be disabled by default, I think it's unlikely to be the cause.

Have you tested the browser's safe mode?

[tanquang]

Have you tested the browser's safe mode?

I haven't tried safe mode but I tried removing the "--disable-zero-copy" flag when starting the browser, nothing changed.