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 have been annoyed for months with memory ram being consume a lot on Steam client process and those steamwebhelper and yet Steam support couldn't help about any circumstance whatsoever.
They have however sent me a possible solution to ''soft reset'' the consumption when entering on Big Picture mode and then quitting back to desktop but didn't work either.
I have eventually discovered a way to calm things around but not sure if this trick will work on all Operating System but Windows 7 Professional.
There are usually about ten Steam processes (Client WebHelper, ClientService...) and each one consumes 0.2% of CPU, when bugging instead (even after closing the program correctly) there is only Steam Client Bootstrapper which consumes a lot of CPU and another process).
I use Windows 10.
If you not entirely sure what you're about to be doing then open a ticket on Steam and try to reason there may have an issue with Steam client or with the most recent update released last night and wait for a response.
I 'End Tasked' this Process in Task Manager and was all good for a while then about an hour later i had to do it again.
Just noticed a similar thing happen today while Browsing and watching some Youtubes, Steam Webhelper using about 1.6GB of Ram.
I never recall it ever catching my attention inTask Manager as a consumer of Ram as its only ever been in the few Hundred MB area.
I take it this is some Steam bug that has appeared of late?
Just Ended said Process before typing this and already its up and running again at 275mb lol
(I never had this problem, so can't tell for sure)
even i try to block webhelper but problem is its allowed through steam.
you might want to ask steam, clear cache on exit , same as browser do it,
not sure how steam support not know this, or have not learn all browser has that option.
i think i did block it right way , problem is can you even kill it or is that even the right solution, i bet it will hurt other web releated issue.
to my knowledge that is a choise in every Browser MS edge to firefox / chrome, im not sure how they can not know this.
even ccleaner and other help app hunt down that cache issue.
Tracking the misbehaving Steam Webhelper process through Task Manager leads me to the:
cef_log.txt file
Which contains nothing but the cef_log.previous.txt file contains the actual Data which is showing a lot of Warnings for:
3316 Received HEADERS for invalid stream
672 Failed to read DnsConfig
Don't know how much help this will be to others but gonna reboot Router, Removing Caching & Cookies from Steam Client and Browsers ect, can't hurt :)
This issue is Rare and I suggest you to try this steps
*Reinstalling Steam
*Changing skin to a different one (either stock or custom depending if you are already using one or another)
*Deleting every file on Steam folder but Steam. exe, steamapps and userdata (this will reinstall without losing data or games)
*Preventing Steam from using all CPU cores and making it use only one of them
*Disabling Ingame Overlay
Those didn't work for me, that's why I started to tweak things and try to find out on my own. Here is what I did and finally reduced my Steam CPU compsumition:
*Open steam Settings
*Go to Controller section
*Open General Controller Settings and deactivate/activate some options before exiting,
In the same menu, make sure you deactivate Guide Button option (the first one)
*Open and close Big Picture Config
*Open and close Desktop Config
*Open and close Guide Button Sequence Settings
I hope this will help you :)