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
Say it was 100 processes, and?
The client uses Chromium, that's why you're seeing several processes. It works in a similar fashion to Chrome that you mentioned in your OP.
My Steam usually hovers between 350-500Mb at the most. It used to be 200-350mb, so it did grow in size, but it hasn't impacted performance in any way on this old laptop.
You might want to check out the game though, I've had games in the past which refused to properly alt-tab or even do it at all.
Alternatively you could try using the web browser in the overlay depending on what you're trying to check.
https://steamcommunity.com/groups/SteamClientBeta/discussions/0/616187204015705442/#c1696043806576878680
For starters, a process that's not doing anything takes no CPU. This is why your task manager shows all those processes with 0% CPU usage -- they are just sitting there, waiting for something to happen.
Now, as for the processes themselves, the code segment is shared -- so, whatever code they are executing is only loaded into RAM once. Beyond that, however, depends on what these processes do: they may or may not share some of their data.
In extreme cases, like the aforementioned "something" not happening for ages, their code might even be unloaded and their data might be placed on swap, leaving only a few bytes of actual RAM use.
Using processes is generally more complicated than threads (unless you're actually launching a separate application, but I don't think that's what's happening here), so there's probably a good reason for doing it.
Small mode does nothing with the process spam, even when it only displays the list it still has 7 processes and sits on all the memory.
Clearly shows the devs don't give a ♥♥♥♥ about the client and have no sense of "reasonable". :(
I'm always amazed at how bad all these professional developers are, if you're going by every layman's opinion...
Been for years now with the Chromium browsers, obviously client software build on Chromium will have the same behaviour.
You're literally trying to paint normal behaviour as a "problem".