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
I am not using Beta version by the way..
As a workaround, you can remove that post (or all of them) from the what's new section. This wont fix the underlying issue, but it should stop Steam eating your system resources for now.
Note that, even if you are using the small mode the what's new section is still loaded by Steam causing this issue.
Edit: It would appear that the "Fat Scout Shootout Tournament" event post has now been removed by Valve. However, these post are personalized so this post could be gone just for me.
Edit 2: This may be an issue specific to "In-Game Event" posts in the what's new section. If you still have this issue, try removing all "event posts" from from what's new.
After restarting Steam, it started to bloat back up again, hitting half a gig in 15 minutes and chewing 2~5% CPU again.
I keep steam in the old 'mini' style. I went to "Large Mode" after seeing this and it was on Library. Clicked to Store and it stopped and settled down.
[EDIT]
Scratch that. As soon as I minimized it back to tray, it returned to binging on ram and CPU.
Before it was usually at 5.4/16gb and now it's growing up to 9/16gb gradually without doing anything.
For now on, I have to run no-browser command from memory consumption.
It is off.
It was that "Fat Scout Shootout Tournament" ad thing. Removing it stopped it completely.
Yes, getting rid of the whats new posts in the library is what worked.
https://steamcommunity.com/groups/SteamClientBeta/discussions/3/2962768084999967276/
Had 2 of them max one cpu core each today. Clearing the what's new section solved the issue, now all steamwebhelper processes are at 0% and games are running smoothly once again.
I agree. The steamwebhelper CPU usage and memory consumption still need resource optimization and mitigations.