Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
To summarize: You did this. Don't do that and it won't happen.
I have literally never opened the in-game Steam web browser, lol. There are many reports of the new Steam UI taking much more RAM than the previous, but never to this degree.
I've killed the 4gb process and just by going to this discussion from within the Steam client, I'm back up to 2.6gb.
i also closed community feeds and deletes categories on startsite :P
Because Steam have massive memory leaks and add 200/300 megabytes every time BPM or the controller UI is launched and then closed.
That was reported when in beta but never addressed.
Nah, never used BPM or the Controller UI, but good to know.
Ok, that I understand. However, my usage with Steam generally hasn't changed. I'm not navigating to pages more often than usual. I monitor RAM pretty frequently, and with the old UI my usage never even climbed to half of this. Regardless, I would've hoped there would be some garbage cleaning in place where Steam recognizes I haven't been to those pages in a long time and unloads them from RAM. Something the old UI appeared to do(because the RAM footprint was never this high), but this new one doesn't.
But now....
Has little to do with it.
The baseline consumption is higher.
I could (and still can, with the -vgui parameter...) visit the community forums and post here from the client and it'll remain around 250~300 MB RAM consumption on a 32 GB system.
If I launch just the library and leave it sitting there on the new client, it'll already consume 500~550 MB RAM.
Apart from the baseline consumption being higher, the new client also has a number of known memory leaks.
The controller configuration UI and BPM have already been mentioned.
But it also leaks on viewing certain store content.
And it leaks when viewing artwork in the community hub.
Part of these leaks existed in the old client as well, but weren't really an issue there.
Only in the new client do they become an issue because the leaks are exacerbated by the fact that the new client uses one single web view to present everything. It and all its tabs; are kept alive for the entire duration the client is running. Whereas with the old client using the VGUI application shell, it would switch between different views and allow memory to be reclaimed because 'tabs were closed.'
Thank you for that explanation. With the way the new client loads everything into one webviewer process, I can now track the more I look at community content, the larger the process gets and it never terminates because it doesn't have multiple tabs as you said. Really hope this behavior is fixed..but it sounds like this UI was in beta for awhile and many issues weren't addressed.
In order to keep RAM usage down I've just disabled all community content loading.