search

win32ss / supermium

Chromium fork for Windows XP/2003 and up
https://win32subsystem.live/supermium/
BSD 3-Clause "New" or "Revised" License
2.46k stars 85 forks source link

[Crash, regression] Browser v126 now crashes on start in single-process mode (v122,v124 was ok) #894

Open IDA-RE-things opened 2 months ago

IDA-RE-things commented 2 months ago

Describe the bug v126 (any release) now crashes on start in single-process mode. While previous v122, v124 versions works ok with it (with known issues of couse). Crash not depends on present of DWrite.dll; Without it it also crashes. This not allows to debug browser in single-rpocess mode, when its requered.

To Reproduce Start with --single-process mode command-lie switch

Screenshots screen1 screen2

Desktop:

Ravenant1234 commented 2 months ago

i can confirm that This doesnt happens in Windows 7 x64 supermium 32 bits

IDA-RE-things commented 2 months ago

This doesnt happens in Windows 7 x64

On my Win7 x64 --single-process not works at all: not with current v126, not with previous versions (#594). Are you sure, it works ? Then it will be machine-dependent. Please re-check.

win32ss commented 2 months ago

I have successfully tested version 126 in --single-process mode on Windows XP (x86 and x64), 7 and 10. So I will put it in the floating category.

Another issue was also reported with 126 on Windows 7. It was not in -`single-process mode, but the dumps indicated the failure was related to a bad renderer message (#870).

Half-Modern commented 2 months ago

Windows 7 x64, 32-bit version of Supermium, profile carried from another PC, --single-process loads the window briefly (mostly not enough time to render it completely) and it exits. Same system and browser, but this time a profile created on that PC, --single-process loads the browser, but when I try to visit a site, it exits (I call it exit since it doesn't show up the "Program has stopped working" dialog). I will update if I also test it on XP x86. Update: well, crash happens when I click on "Dark Reader" plugin to try to edit the settings because the images etc. don't show up (I believe it's caused by the malfunctioning extension), so I think it breaks some extensions (Like it did break Ublock Origin on previous versions). @IDA-RE-things: Can you test --single-process on a new profile without extensions and try to start without --single-process but --in-process-gpu? I'd like to know if it's related to GPU process running in the main thread.

IDA-RE-things commented 2 months ago

Have rechecked this for Win7 x64: (Note that on my machine here DX9-only CPU-integrated NVidia GFX used, which nevertheless has Video decode acceleration).

So, Starting Supermium v126-r3 32b-bit with a clean profile:

So the problems as I see:

IDA-RE-things commented 2 months ago

I have then checked the crashdumps, and found that for both above crashing modes the callstacks and errors are same (libANGLE):

screen1 (inprocess-gpu) screen2 (inprocess-gpu)

Half-Modern commented 2 months ago

Have rechecked this for Win7 x64: (Note that on my machine here DX9-only CPU-integrated NVidia GFX used, which nevertheless has Video decode acceleration).

Unfortunately Google blacklisted certain versions of drivers from using Video Decoding function, as it works on Brave which is based on Chromium 78 but not on newer versions. I think removing the blacklist would just be enough since I am able to use video decoding of my desktop's GPU, GT 640 with 4xx.xx something drivers.

So, Starting Supermium v126-r3 32b-bit with a clean profile:

--single-process -- starts and closes with a crash.
--in-process-gpu -- also starts and closes with a crash
no above switches -- starts and works as expected (but in Software only mode)
--ignore-gpu-blocklist --use-angle=d3d9 : starts and works, using HW acceleration
--ignore-gpu-blocklist --use-angle=d3d9 --in-process-gpu : starts and works, using HW acceleration and no additional GPU process (as expected)
--ignore-gpu-blocklist --use-angle=d3d9 --single-process -- starts in single-process mode, using HW acceleration. (as expected)

Very interesting. My both profiles use GL, but somehow one crashes while the other one works.

oleedd commented 2 months ago

as it works on Brave which is based on Chromium 78 but not on newer versions

Release Notes v1.69.168 (Sep 11, 2024) Upgraded Chromium to 128.0.6613.138. https://brave.com/latest/

Half-Modern commented 2 months ago

I'm running Windows 7

IDA-RE-things commented 1 month ago

UPD: have checked with latest v126-r4 : result is same. Also I have found, that problem appears only if extensions installed (which one I have not detected while). Without extensions on clean profile browser starts in single process succesfully.

But v122 and v124 releases have no this problem. And it was working with my existing extensions and profile.