136.5.5.3 beta-2 issues

[redfox]

136.5.5.3 beta-2 issues:

- some GPU's moved to the block list now, need to enable chrome://flags/#ignore-gpu-blocklist to keep the GPU acceleration
- higher CPU usage, when playing videos, when compared to version 135.5.4.3 (with GPU on)
- higher memory consumption, when playing videos, in my case about +25%
- Catsxp task manager does not show CPU usage of processes, when opened for first time; need to close and open again

[catsxp]

Graphics card driver issue The graphics card is too old, the driver is not being maintained, and many problems have not been solved

[redfox]

Its an integrated GPU Intel Graphics 610, which never had official drivers released for Windows 7, because the CPU (Kaby Lake) officially supports only Windows 10. But it works, including acceleration.
Google only pushes users to buy new HW, like other producers, including MS.

But, it does not change the fact, that the Chromium core 136 is worse than 135.

[catsxp]

Try fix issues
Do not change the flags(chrome://flags/#ignore-gpu-blocklis)
Test 5.5.3 beta-4

[redfox]

136.5.5.3 beta-8
Problem not fixed, still 3 new dump files just after startup, more following...

Version 135.5.4.3 no errors, no dump files.

[catsxp]

Add startup parameters
--disable-direct-composition

test!

[catsxp]

try beta-9

[redfox]

No change

[catsxp]

try
https://vip.123pan.cn/1811655563/catsxp ... _3_9_1.zip
https://vip.123pan.cn/1811655563/catsxp ... _3_9_2.zip
https://vip.123pan.cn/1811655563/catsxp ... _3_9_3.zip

[redfox]

beta 9, 9.1, 9.2, 9.3
Still the same, 3 dump files right after startup, blank pages.

The difference from version beta-8 is, that beta-9 crashes even with the flag chrome://flags/#ignore-gpu-blocklis set to enabled.