UPDATE:
Mr E3kskoy7wq the developer of Chromium-for-windows-7 said:
"Understood. It appears the issue was introduced between chromium/chromium@be77d57 and chromium/chromium@d5222f4. However, there are 560 commits between them, making it difficult to pinpoint the exact culprit. I’ll proceed with further bisecting to narrow it down.
I want to test whether the following versions also have this issue:
https://github.com/e3kskoy7wqk/Chromium ... 2.0.6780.0
https://github.com/e3kskoy7wqk/Chromium ... 2.0.6787.1
https://github.com/e3kskoy7wqk/Chromium ... 2.0.6793.0
https://github.com/e3kskoy7wqk/Chromium ... 2.0.6813.0
Starting from version 132.0.6781.0, Chromium upgraded its required Windows SDK version from 10.0.22621.2428 to 10.0.26100.1742 (chromium/chromium@0f6eaa5), then downgraded it back to 10.0.22621.2428 in version 132.0.6811.0 (chromium/chromium@ea1232d). However, in chromium/chromium@fca8e87 (included among those 560 commits), Chromium again upgraded the Windows SDK version to 10.0.26100.3323.
My concern is that this issue might be caused by the Windows SDK version upgrade. If that's indeed the case, resolving it would be particularly challenging.
I'd like you to help confirm this hypothesis. If the issue is truly SDK-related: versions 132.0.6787.1 and 132.0.6793.0 should exhibit the problem and versions 132.0.6780.0 and 132.0.6813.0 should be unaffected. If the issue is unrelated to the SDK upgrade, then none of these versions (132.0.6780.0, 132.0.6787.1, 132.0.6793.0, 132.0.6813.0) should have the problem.
I would like to know whether version 136.0.7081.0 (commit 5c4a5d12a032509f15daeec1c036dace785bc9bf) exhibits this issue.
https://github.com/e3kskoy7wqk/Chromium ... /tag/debug
Please also test these previously mentioned versions:
https://github.com/e3kskoy7wqk/Chromium ... 2.0.6780.0
https://github.com/e3kskoy7wqk/Chromium ... 2.0.6787.1
https://github.com/e3kskoy7wqk/Chromium ... 2.0.6793.0
https://github.com/e3kskoy7wqk/Chromium ... 2.0.6813.0