An absolute disaster: illegible writing, illegible settings menu, accent color that hides the writing...

[drimisone]

Mr @Catsxp, i have D3DCompiler_47.dll on my os, and Mr. @e3kskoy7wqk said :


"From what I understand, d3dcompiler_47.dll only affects performance and isn't the cause of this particular issue. (See: #45)"

https://github.com/e3kskoy7wqk/Chromium ... 2868908307

[catsxp]

It needs to call system functions to complete tasks, and higher versions may call functions that the system does not have or use unreasonable parameters, resulting in execution exceptions

[drimisone]

Yeah; I know this is very difficult, thanks for all your efforts Mr @Catsxp!

I'm thinking of reinstalling Windows 7 OS Full Edition, but first I need official confirmation, before I reinstall Windows 7 OS Full Edition from scratch, that new Chromium versions will work on Windows 7 OS with full patches. For now, I have Firefox Nightly 140 and Supermium, I prefer to wait for the final and definitive resolution of this mystery, thanks

[catsxp]

Respect users' right to choose, use it if you can, and switch to a browser if you can't. There are plenty of choices, and catsxp will not be the only choice for users.

[drimisone]

Yes, I'll wait and try the new future versions of Catsxp, thank you!

As a precaution, I'll contact the developer of vxkex and ask him to add Catsxp to the official list of supported softwares !

[drimisone]

Update :

it seems the problem affects iGPU only :



"The build at https://github.com/e3kskoy7wqk/Chromium ... .0.7103.96 was compiled with the new SDK and has no noticeable issues besides this one - you can use this version for testing.

Additionally, I'm currently building version 138.0.7172.1 with the old SDK. The process is going smoothly so far. If this resolves the issue in 138.0.7172.1, I'll consider the solution successful (though not ideal) and will rebuild version 136 accordingly.

I prefer to draw conclusions after thorough testing rather than making definitive claims prematurely.

-@e3kskoy7wqk

Any idea how this would explain why only some people are impacted by this issue? Because I'm entirely unable to reproduce this issue at all. I've tested all, to me, possible hard- & software configurations. The only setup I couldn't test is an Intel iGPU based system, as I lack that kind of hardware.

This is terribly interesting to me.


-This is also a mystery to me!

If I could reproduce it and knew the reason, I would have no need to use a bisection and publicly ask everyone to test it, let alone resort to downgrading the SDK to solve the problem.

We need a smart person to solve these puzzles."

[drimisone]

Update :

here my response :


"I think I have Intel iGPU, i.e., a graphics card integrated into the CPU. I don't have a separate GPU in my EEE PC. I have an Inter(R) Graphics Media Accelerator 3600 series. If Intel Graphics is causing the problem, maybe delete in the source code hardware acceleration? I disabled hardware acceleration in Chromium 138, but the display problem persists in Chromium 138. I think it's a font issue. I saw that Chromium 136 added a new flag : font enhancement smooth anti-aliasing......

Perhaps change the font size in the source code of Chromium 138 because I see the zoom indicator sometimes stuck at 0? i cant't zoom in 120% or 80% for example,

I disabled Windows Aero and Font Smoothing in my Windows 7 OS to improve performance.....

Mr. @e3kskoy7wqk, I previously said that letters do not appear or are out of order : this is no longer a major issue for me and what I'm interested in is to be able to installing video downloader extensions in the recent Chromium kernel because a video downloader extension developer recommends using the latest version of Chrome, and Chromium allows temporary video display while downloading, while Firefox doesn't.

So, I just installed the Chromium 138 exe version. The first thing I do is visit my favorite streaming website:

https://v6.voiranime.com/anime/enen-no- ... i-3-01-vf/

I can pass the recaptcha and playback the video, thanks!

Now I'm installing Live Stream Downloader extension :

https://chromewebstore.google.com/detai ... fekj?pli=1

And unfortunately, Chromium 138 suddenly closes.

so letters don't appear or are out of order= this isn't the real disaster anymore. The real disaster is that we can't install our video download extensions in Chromium 138. We hope this problem will be fixed, please. I will open a new issue about this major issue. I also mention Mr. @chandler-stimson to help us debug this LSD installation problem in Chromium 138.0.7169.0 (32 bits) please:

https://github.com/chandler-stimson/liv ... downloader

https://github.com/e3kskoy7wqk/Chromium ... 8.0.7169.0

[drimisone]

Update:
Here my new response in the issue in chromium for windows 7 repository :


I was surprised when @Mr. @e3kskoy7wqk t told me: "

The build at https://github.com/e3kskoy7wqk/Chromium ... .0.7103.96 was compiled with the new SDK and has no noticeable issues besides this one - you can use this version for testing."

I thought Mr. @e3kskoy7wqk compiled a new debug version, but the link points to stable Chromium 136.0.7103.96, i.e., the first version of Chromium 136 that I tested and where I saw the issues and display problems, and I obviously informed Mr. E3kskoy7wqk!

Maybe Mr. @e3kskoy7wqk got the wrong link?

To clear up any doubts, I downloaded the exe version of 136.0.7103.96 again, and it launches, but there are display issues!

So, 136.0.7103.96 has display issues, so I think the new Windows SDK version caused the problem. I'm surprised that Mr. @e3kskoy7wqk says that 136.0.7103.96 was compiled with the new SDK and has no noticeable issues besides this one, because obviously there are display issues problems in 136.0.7103.96, mentioned previously!

Thanks for the new debug versions ! I'm taking a break and then testing the new versions,thanks !"

[drimisone]

Update :

a user says : "I can confirm that the issue affects Intel iGPUs. Mine is Intel HD Graphics 610.
But, as I wrote before, installing KB4019990 helped completely - no errors, no dump files."

another user says : "Your fixed 138 version works for me. My GPU is an ancient Intel G41 Graphics Express Chipset (GMA4500)."


and here my response :


" i install this new debug version :

https://github.com/e3kskoy7wqk/Chromium ... taller.exe

i mean i install chromium Version 138.0.7172.1 (Build officiel) (32 bits) and there is no problems, no issues, everything is ok !

Update :

Mr @e3kskoy7wqk , i note interesting thing :

in chromium 138.0.7172.1 with the previous SDK version , we can install extension like LSD :

https://github.com/e3kskoy7wqk/Chromium ... taller.exe

but in chromium 138.0.7169.0 with the new SDK version, i can't install extension like LSD, the browser close abruptly when i install extension :

https://github.com/e3kskoy7wqk/Chromium ... 8.0.7169.0

i fear the upgrade of the SDk version not only ruins the display but also destroy the ability to install extensions !

[drimisone]

UPDATE:

I might cry with joy, AlhamdoulilAllah! I just rechecked again on my KB updates, and yes, I have KB4019990 installed! I didn't notice this KB update patch because I have a small screen and there are a lot of KB updates, so what's certain is that it's not the lack of KB4019990 that's causing this bug Mr @Catsxp !