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
To add on to that, each webhelper covers their own area in the client.
One for the store, one for community, one for the library etc..
this has nothing to do with how many cores Steam uses and Steam also will not use all of your cores by design.
------------
Steam is using https://en.wikipedia.org/wiki/Chromium_Embedded_Framework
at the design core, Steam is a web browser, like chrome, firefox, edge, opera, etc. it is common software procedure for web browsers to put things in their own process container for multiple reasons surrounding security, stability and resource management.
it is a little bit more complicated than bloodshed said because it is mostly more diverted by tasks and not by "tabs", like one task paints the page, another task does the javascript stuff and so on. so like chrome and firefox, you do not have 100 tasks when you have 100 tabs open, you have a few dozen or so and processes will be added or killed if sub tasks are required or not for ongoing things on a page, like f.e. an animated gif.