Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Just like how chrome spawns separate exe for each tab
Remember Steam is a browser built on top of an application
Functionally the RAM usage is going to be identical. Aka the minor overhead of spawning multiple exe is minimal just like in chrome, compared to the benefits of separate exe handling web requests. Either its one giant exe ro a bunch of smaller ones.
http://steamcommunity.com/groups/SteamClientBeta/discussions/1/38596747699743095/#c38596747712498912
Now there's 3 helpers...... 2 more then normal....
Note that your library will cycle through your screenshots in large mode which is effectively a web session back to your screenshot library on the cloud
I'd say at a bare minimum you'd have 2 on startup, the main controller process and one sub-web process just as a starting hook.
Also note that likley all this was happening before, you just didn't see it because it was in a single exe.