mockingbird

Just replicate my conditions: -multiprocess mode enabled -direct3d enabled and forced, webgl enabled and forced Graphics card is 7th generation nVidia. Open a private window, launch youtube Open a normal window, launch youtube browse around for a little and it will crash. In Thorium, everything is ok -- it acts strange because it runs out of memory with too much stuff open, but it is usable.

I get error with vcruntime140.dll after a while putting it through its paces.

@feodor2 Do this: Go to youtube. Next, open a private window and open youtube. Log into your account on youtube in the private window. Do this for a while and browse websites in the normal window... Eventually, it will crash after a day.

Try getting a later version and modify the INF with your device ID and then force install it and see if that works.

6200 should be supported... Anything DirectX 9 should work. Try updating your driver.

It's working great for me...

Look what came out today: v1.2.0.5058 (2024.05.28) [+] XP: Added support for Hardware Accelerated rendering for XP. With it, browser will use less CPU to render pages, and while playing videos. To use, run it with switches: --use-angle=d3d9 --ignore-gpu-blocklist. With it, you will see this features in about:gpu for XP, as you see it on NT6+ systems. Wow! Time to test this out!

@Fedor - The latest version crashed for me after a while on vcruntime dll... It was stable for a day though... I set the tab process count to 3 from 1, maybe that's why. I have to go back to Thorium for now.

Look through RLOEW's patches for the VFAT fix... It occurs when you have is memory patch installed and then install a network card.

I spoke too soon on 68.14.1b and it did indeed crash on xul.dll for me, so I'll give this one a shot. Thanks

Chalkboard is a very old (>10 years) benchmark released by Microsoft for IE10... HWACCEL (notify me if you want this benchmark) is an even older benchmark released by Mozilla ages and ages ago when they started experimenting with DirectX 9 support for Firefox. HWACCEL is great for testing whether layer acceleration is working and I find it useful for checking whether MyPal is functioning correctly (MyPal is now what I consider to be stable and also supports DirectX9 acceleration, but it is far, far slower than Thorium on XP). Chalkboard and HWACCEL are not what I would consider to be benchmarks today, but rather sanity checks to see if the browser is functioning correctly since they are experimental by nature. If Chalkboard is underperforming in Thorium or HWACCEL in MyPal then it's an easy way to know right away.

check out "chrome://flags" and "chrome://gpu". In flags, you can disable rasterization manually without touching the acceleration settings in Chrome and then verify the result in chrome://gpu. FYI, I ran some more tests to demonstrate what I was saying before about benefiting from disabling hardware rasterization on older GPUs. In all cases, the CPU is a 4th gen Haswell. For the iGPU, the tests were run on Windows 7. For the 1660, it was run on Windows 10. iGPU with rasterization enabled: iGPU with rasterization disabled: GeForce 1660 with rasterization enabled: The GTX1660 is about 5 times faster in Chrome than the integrated GPU and about twice as fast as the GCN 1st Gen Radeon HD7770 (the HD7770 test was done with Thorium AVX on a 3rd gen Ivy Bridge though, but that probably doesn't make any difference). Who said software rendering was dead?

@feodor2 - I must say the latest version (68.14.1b) is working great for me so far on XP. I have D3D and Multiprocess enabled and so far it is completely stable. I'm very tempted to use this instead of Thorium. Great job!

It's been like this for ages -- years... A minor version update won't produce a different result... In my opinion, Chrome GPU rasterization is hit and miss when it comes to GPUs. For 4th generation Core CPUs (haswell) IGP, I turn it off. I leave it on for the Radeon HD7770 even though it's twice as slow as software rasterization.