-no-browser was removed...

https://gtm.steamproxy.vip/groups/SteamClientBeta/discussions/3/3710433479207750727/

Yup.

Despite significant protests, Valve removed the option to start Steam without CEF. And if you read the official notice: they are in fact doubling down on it and are planning on moving more and more over to the browser runtime. That is why they removed the option. Its continued existence was an impediment to safely moving more functionality into the browser runtime.

Of course the fact that the browser runtime continues to suck up a major amount of system resources or flat out just doesn't want to work properly at all for some users, that's just unfortunate collateral damage. Ey; what's a few thousand customers affected on the scale of millions, right? /s

Originally posted by RiO:

Yup.

Despite significant protests, Valve removed the option to start Steam without CEF. And if you read the official notice: they are in fact doubling down on it and are planning on moving more and more over to the browser runtime. That is why they removed the option. Its continued existence was an impediment to safely moving more functionality into the browser runtime.

Of course the fact that the browser runtime continues to suck up a major amount of system resources or flat out just doesn't want to work properly at all for some users, that's just unfortunate collateral damage. Ey; what's a few thousand customers affected on the scale of millions, right? /s

Bold text in quote added by me:

Wellll - depending on the actual number of customers affected and from a purely business review based on a realistic cost/benefit analysis - then - yeah - right.

Edited to Add: @RIO - I've read not a few posts by you in a number of different threads. You seem to be exceptionally knowledgeable concerning STEAM/Valve technical operations.

What's your DEAL man? Who are you and how do you know what you know about STEAM/Valve?

okay that sucks.... thanks for the info.

I wrote a script that allows you to semi-return (without a functioning friend chat) this behavior:
start-mini.cmd

start-full.cmd

You must change D:\Games\Steam to your steam path.
If steam is in program files then you must run the scripts with admin rights.
At the same time, due to runas /trustlevel:0x20000, Steam will start with drop admin rights.

You must run start-full.cmd at least once if you want full functionality back, otherwise without it there will be an integrity check when trying to run steam normally

Actually they could reduce these processes to 1-3 additional process and cut down its memory consumption, but either they do not have specialists who can do it or they are not interested in it.

I also recommend that you turn off "Enable GPU accelerated rendering in web views" in the Interface section of the steam settings.
This will turn off the consumption of expensive video memory.
Modern processors are enough to draw pages quickly.
You will also save another ~150 megabytes of RAM.

Originally posted by cSg|mc-Hotsauce:

-no-browser was removed...

link

:qr:

why do you always put that qr code at the end of all of your comments?

Originally posted by NightFox:

Actually they could reduce these processes to 1-3 additional process and cut down its memory consumption, but either they do not have specialists who can do it or they are not interested in it.

You can run Steam with the single CEF process commandline option, but it just makes everything crash all over the place.

Originally posted by NightFox:

I wrote a script that allows you to semi-return (without a functioning friend chat) this behavior:
start-mini.cmd

@echo off cd /d "D:\Games\Steam" rename .\bin\cef\cef.win7x64\steamwebhelper.exe2 steamwebhelper.exe rename ./bin/cef/cef.win/steamwebhelper.exe2 steamwebhelper.exe rename .\steamerrorreporter.exe2 steamerrorreporter.exe rename .\steamerrorreporter64.exe2 steamerrorreporter64.exe runas /trustlevel:0x20000 "steam.exe +open steam://open/minigameslist" :search tasklist|find "steamwebhelper.exe" IF %ERRORLEVEL% == 0 GOTO :found TIMEOUT /T 5 GOTO :search :found rename .\bin\cef\cef.win7x64\steamwebhelper.exe steamwebhelper.exe2 rename .\bin\cef\cef.win7\steamwebhelper.exe steamwebhelper.exe2 rename .\steamerrorreporter.exe steamerrorreporter.exe2 rename .\steamerrorreporter64.exe steamerrorreporter64.exe2 taskkill /f /im steamwebhelper.exe del .\bin\cef\cef.win7x64\steamwebhelper.exe del .\bin\cef\cef.win7\steamwebhelper.exe del .\steamerrorreporter.exe del .\steamerrorreporter64.exe

start-full.cmd

@echo off cd /d "D:\Games\Steam" rename .\bin\cef\cef.win7x64\steamwebhelper.exe2 steamwebhelper.exe rename .\bin\cef\cef.win7\steamwebhelper.exe2 steamwebhelper.exe rename .\steamerrorreporter.exe2 steamerrorreporter.exe rename .\steamerrorreporter64.exe2 steamerrorreporter64.exe runas /trustlevel:0x20000 "steam.exe +open steam://open/largegameslist"

You must change D:\Games\Steam to your steam path.
If steam is in program files then you must run the scripts with admin rights.
At the same time, due to runas /trustlevel:0x20000, Steam will start with drop admin rights.

You must run start-full.cmd at least once if you want full functionality back, otherwise without it there will be an integrity check when trying to run steam normally

I've stolen and slightly modified your code for https://gtm.steamproxy.vip/discussions/forum/0/3758852249527312123/ FYI.



I think it would be worth trying if you can deny permissions at runtime, like https://gtm.steamproxy.vip/groups/SteamClientBeta/discussions/3/3710433479207750727/#c3763356482613719068 but with cmd/bat/ps1/vbs/whatever script files.

Originally posted by Wolfsun:

Edited to Add: @RIO - I've read not a few posts by you in a number of different threads. You seem to be exceptionally knowledgeable concerning STEAM/Valve technical operations.

What's your DEAL man? Who are you and how do you know what you know about STEAM/Valve?

I'm just a software engineer. Not employed by Valve or anyone else in the gaming space.
Just someone with a considerable pool of technical background knowledge, whose been around the block a fair few times; has been a customer with Steam long enough to see how they've operated over the years; and tends to keep abreast of what's floating about in the Steam beta forums.

Nothing more.

Most I post on topics like this are educated guesses based on my knowledge; scraps I lifted from other user's reports; and the ability to connect the dots on those. Note that I still use phrasing like 'likely' or 'probably' a lot of times - 'cuz ultimately you cannot be sure without actual access to the chef's kitchen. ;-)

Originally posted by luckz:

Originally posted by NightFox:

Actually they could reduce these processes to 1-3 additional process and cut down its memory consumption, but either they do not have specialists who can do it or they are not interested in it.

You can run Steam with the single CEF process commandline option, but it just makes everything crash all over the place.

Oh, that causes Steam to actually crash now?
Good. Because you wouldn't want to use that anyway.

It disables the browser's security sandbox, and the version of Chromium that Steam uses is old and susceptible to numerous exploits. Including a dangerous remote code execution vulnerability that was already being exploited to target another Valve product, namely:
DOTA 2.

DOTA 2 uses the V8 JavaScript engine for some things; the same engine that Chromium uses. DOTA used an old version that was still susceptible. Chromium was patched to use a fixed version of V8 that no longer has that vulnerability with version 95, some 15 odd months ago. But Steam is still using the 2.5 year old version 85 of Chromium, afaik.

Originally posted by luckz:

You can run Steam with the single CEF process commandline option, but it just makes everything crash all over the place.

The standard single process mode (--single-process) is an unsupported and obsolete mode which has been broken for a long time in chromium.
How can the command line for these processes be passed?
If you know how to pass it try passing: --renderer-process-limit=1 --in-process-gpu --process-per-site --disable-gpu

Originally posted by luckz:

I think it would be worth trying if you can deny permissions at runtime, like https://gtm.steamproxy.vip/groups/SteamClientBeta/discussions/3/3710433479207750727/#c3763356482613719068 but with cmd/bat/ps1/vbs/whatever script files.

Yes it is possible, I forgot about it.
There is an icacls command.
I'm a little lazy to do it now, try it yourself. icacls /?

Steam has its own versions of these cmds, they tend to include CEF
like
-cef-single-process -cef-in-process-gpu -single_core -cef-disable-d3d11 -cef-disable-sandbox -disable-winh264 -cef-force-32bit -no-cef-sandbox

(I should mention that some prevent Steam from starting. Maybe it was forcing 32bit if you don't even have 32bit webhelpers? I forget though.)

Originally posted by luckz:

Steam has its own versions of these cmds, they tend to include CEF

Thanks. I found the keys in chromehtml.dll

By the way -cef-single-process works for me, no crashes. CEF here is apparently quite old where a single process is still running, or they fixed something.
But the memory gain is only ~100 megabytes, steamwebhelper will still eat ~190 minimum (on start).

Originally posted by I_AM_Y33T-B0I_1000:

Originally posted by cSg|mc-Hotsauce:

-no-browser was removed...

link

:qr:

why do you always put that qr code at the end of all of your comments?

Why not scan it and see what happens? No! Really don't do that. That'd be kind'a like jumpin' off a 1000' cliff to see what's at the bottom.

Originally posted by Wolfsun:

Originally posted by I_AM_Y33T-B0I_1000:

why do you always put that qr code at the end of all of your comments?

Why not scan it and see what happens? No! Really don't do that. That'd be kind'a like jumpin' off a 1000' cliff to see what's at the bottom.

Or just use the search function...

https://gtm.steamproxy.vip/app/257510/discussions/0/626329187174110840/