-no-browser and -noreactlogin removal

[UFeindschiff]

Your system information

• Steam client version (build number or date): Dec 19 2022, at 22:01:34
• Distribution (e.g. Ubuntu): Gentoo
• Opted into Steam client beta?: [Yes/No] Yes
• Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

The latest Steam Client Beta removed support for the -no-browser and -noreactlogin flags with the client giving a warning about their removal and the instruction to inform Valve in case that causes any issues which is exactly what I'm doing here.

There is still an open issue with steamwebhelper having a memory leak, leading to insane amounts of memory usage after some time (issue #7266 ). As this issue is currently still unfixed, removing the only workaround (disabling the web component) seems like a very bad idea as it leaves users like myself with a Steam client which eats up multiple gigabytes worth of memory after a few hours of running in the background. While I personally have 128GB of memory installed and therefore it's not the end of the world if Steam uses 10 of them, people with less memory will most certainly greatly feel that impact. I therefore ask to either keep/bring back the -no-browser and -noreactlogin flags until that issue is fixed.

Another thing worth noting: If hardware is ever mentioned in any of the many reports about the steamwebhelper not working properly, most often an nVidia GPU is installed (as is on my machine). Maybe it's some issue about CEF not working properly with the proprietary nvidia driver... or maybe it's just one of many Chromium memory leaks which are marked as WontFix in the Chromium bugtracker...

I would ask you to either bring back support for using the Steam client without web functionality or - should you insist that a WebUI is the way going forward - maybe have a fallback embedded browser that isn't Chromium for the people having issues with it.

Steps for reproducing this issue:

1. Start the Steam client and log in
2. Let the client run for a few hours. Maybe browse your library and the store and chat with a few friends here and there
3. Watch as steamwebhelper processes consume gigabytes of memory