Open metapea opened 2 months ago
Please send any crash dumps created in %LOCALAPPDATA%\Supermium\User Data\Crashpad\reports (or wherever the browser profile may be located) as a result of this browser run.
There a older 9mb report that's was made around that time i'm not sure if it's unrelated or not (since i used a crash command for chrome:// before the update), here's the newer crash reports: reports.zip
These reports indicate that there was a "bad" renderer message, which has been reported as being behind various freezes in previous releases on Windows 7. In this case an image's metadata seems to be a problem.
Alright, i guess i wait for the next hotfix and use the Pre-release version in the meantime.
Does it work if you use --enable-features=ChromeRefresh2023
on the command line? Most of the changes between the pre-release and main release were external (DirectWrite and progwrp changes), and the internal ones were mostly limited to theming code.
Does it work if you use
--enable-features=ChromeRefresh2023
on the command line? Most of the changes between the pre-release and main release were external (DirectWrite and progwrp changes), and the internal ones were mostly limited to theming code.
No, i tested the main release version and the command line doesn't work. also the main exe hangs in the task manger after closing as well.
Describe the bug The new release version (126.0.6478.249) just gives me a transparent window (aero) then closes. For the Pre-release of 126.0.6478.249, it works fine. Edit: 126.0.6478.249 R2 doesn't work as well Edit 2: 126.0.6478.254 R4 doesn't work as well
To Reproduce
Expected behavior To open the browser without auto close
Screenshot
Desktop (please complete the following information): Windows 7