STEAM GROUP
Steam Client Beta SteamBeta
STEAM GROUP
Steam Client Beta SteamBeta
26,191
IN-GAME
98,750
ONLINE
Founded
January 8, 2013
All Discussions > Bug Reports > Topic Details
Pedro Lobo Sep 5, 2014 @ 5:10pm
Multiple "steamwebhelper.exe" processes
I've only noticed today.. but maybe this is something that might be from before.

I have now 4 processes called "Steamwebhelper.exe" on my computer.

I don't think this is normal, since steam never had more than 1 process running (excluding the overlay that only activates when playing games)
Originally posted by henryg:
This is intentional. The steamwebhelper.exe helper program, like Chrome, has started using multiple processes for security and stability purposes. If one process crashes, it doesn't take down the entire client; that process just restarts. Likewise, if someone finds a security hole in our website or in the helper's Javascript engine, that exploit might be able to take control of one process - but only one process, and it wouldn't have access to data stored in other processes (like passwords for other sites).

Also note that the total RAM used by these processes is not as high as it appears at first, because the processes share memory with each other. The total RAM is not the same as the sum of all the individual processes. It's difficult to examine exactly how much is shared at any given moment, unfortunately.
< >
Showing 1-15 of 37 comments
Hellrazor Sep 6, 2014 @ 1:37pm 
the same
Empress Misery Sep 6, 2014 @ 11:26pm 
I have the same (using 170, 20, 8 and 7mb of RAM), and the main client is using almost a gigabyte of Ram to do nothing. D:
KingHusky Sep 11, 2014 @ 7:09pm 
Fix This.... Useless Process
CrabbyCliff Sep 11, 2014 @ 9:03pm 
One should have 2 Steam Webhelpers for the main Steam window, and one more for most extra windows.

Even when i have 10+ Steam windows opened at the same time, the processes don't hog my memmory or CPU. Last week however, i noticed the Steam Webhelpers not closing after closing extra windows. That was a one time event, 4 remained active (not hogging). problem solved by exiting and re-opening Steam.

As mentioned, that was a previous build :
Built September 3rd, 12:36:08
Steam API v016
Steam Package 1409777350

Windows 7 x64, Home Premium Sp1
ASUS PC P7H55E
Intel Core I5, 750 @ 2.67 GHz 2.67 GHz
4Gb Ram
AMD Radeon 5670, Primary VRAM: 512 Mb

[edit 13 Sept] Crabbycliff = bumbefly
Last edited by CrabbyCliff; Sep 13, 2014 @ 10:38am
Bumbefly (we/All) Sep 12, 2014 @ 10:30pm 
[update] With 2 extra windows opened after going online, i had 6 Steamwebhelper processes running. 1 disappeared when going back to main UI window.

1 still running at 122.000 to 138.000 kb memory use. I did not notice a single Steamwebhelper process using that much memmory before. the others currently use 7.000 to 20.000 kb, and Steam.exe uses 86.000, as usual when i have Steam active.

(when idle and no extra Steam windows open the webhelper processes commonly use a few hundred kb).

Steam Client
Built September 9th, 14:17:43
Steam API v016
Steam Package 1410299342

[edit 13 Sept] Crabbycliff = Bumbefly
Last edited by Bumbefly (we/All); Sep 13, 2014 @ 10:41am
Pedro Lobo Sep 13, 2014 @ 1:21pm 
some steamwebhelper processes are not closing properly.

This can be a real hasle if you keep your steam active days in a row.
molitar Oct 18, 2014 @ 8:14pm 
New Steam client is utter crap.. Worse coding ever! The app idle in task tray is increasing memory usage for steamwebhelper even while sitting idle.. started at 80+ MB for the 3 dumb exe running.. Now in about 5 minutes it's over 100+ MB alone! Add that to the Steam app itself running over 46MB and it's a stupid memory hog! The coders need to be shot! Using the worse browser in history Chrome with it's memory hogging memory leaks for an app.. Horrible!

And since it's already become the official client can't even opt out of this horrible crap! Bring back the old client it's better than this crap!
Last edited by molitar; Oct 18, 2014 @ 8:17pm
PimpSoBack Oct 20, 2014 @ 12:41am 
Can confirm at present beta still appears to be spawning more steamwebhelper.exe processes than it manages to keep track on and kill off after we close them...

I had 5 steamwebhelper.exe at the same time, one of which was definitely a video since it was 500MB+ but I had already closed the window and yet it had not cleaned up after itself.. please add a check so memory frees up and unnecessary steamwebhelper.exe are killed.. thank you!

molitar you need to check yourself, you're near-criminally overreacting here..
I feel bad for the devs that have to read bile like this and just keep working afterward...
76561198073272592 Oct 20, 2014 @ 3:40am 
SAME PROBLEM....
molitar Oct 25, 2014 @ 8:15am 
It has improved some but it is still not releasing the memory. When I have it open to Library the 3 steamwebhelper is only using about 15MB's total. But when you go to forum or store it shoots up again and close the steam client so it minimizes and the memory will not release even if you go back to the library.

Steam needs to get off the buggy Chrome and use the built in IE in windows as that is a shell of Windows so it won't take that much extra memory to run. I really do not understand why a developer would make a client that has to use a foreign browser as the core and take that much more memory when there already is a native Windows client. I can browse the store with IE 9 and only be using about 40MB total and memory is immediately released upon closing.

Since it won't release the memory it just keeps climbing up slowly!
Last edited by molitar; Oct 25, 2014 @ 8:17am
Bumbefly (we/All) Oct 26, 2014 @ 5:50am 
Indeed this latest Steam Build might have worsened concearning SteamWebhelpers not closing.
See screenshots from yesterday :
https://onedrive.live.com/redir?resid=8900FFCAD5ECFCBB!188&authkey=!AAyEv2h7welEfhE&v=3&ithint=photo%2cjpg,
and
https://onedrive.live.com/redir?resid=8900FFCAD5ECFCBB!190&authkey=!AJcDwooLKWbDh2w&v=3&ithint=photo%2cjpg.

Today i experienced 3 SteamWebhelpers while only being logged in and no Steam window was opened (32.964 kb,10.922 kb and 7.800 kb withSteam.exe at 86.764 kb).

Steam Client
Built October 20th, 14:14:03
Steam API v017
Steam Package 1413917607

Windows 7 x64, Home Premium Sp1
ASUS PC P7H55E
Intel Core I5, 750 @ 2.67 GHz 2.67 GHz
4Gb Ram
AMD Radeon 5670, Primary VRAM: 512 Mb
Network Adapter : Realtek PCIe GBE Family Controller
Driver version 7.46.610.2011 dated 10-6-2011
Last edited by Bumbefly (we/All); Oct 26, 2014 @ 6:05am
Pedro Lobo Oct 28, 2014 @ 9:42am 
I wonder if this is a Windows-only problem..

So far the only OS's posted here are windows, no mac or linux
molitar Oct 28, 2014 @ 6:44pm 
This latest beta is WORSE than ever.. I am watching the process adding 1 MB per miinute which has now reached 94MB of usage! This is utter ridiculous! Even when I close the process so it's only running in system tray it still continues to climb!
Captain_Headrush Dec 4, 2014 @ 3:33pm 
I just couldn't even get on a server in tf2... pop out to windows and find steamwebhelper.exe using 1.7 gb of memory... this is a joke right... I figured out a long time ago to kill the process getting it down to just one which I did... but then got suspicious while having trouble in the client... hmmm



Originally posted by |LP| Tipo:
I've only noticed today.. but maybe this is something that might be from before.

I have now 4 processes called "Steamwebhelper.exe" on my computer.

I don't think this is normal, since steam never had more than 1 process running (excluding the overlay that only activates when playing games)
Виктория Dec 4, 2014 @ 3:41pm 
it's all right! Close thread!
:Kenny:
Last edited by Виктория; Dec 4, 2014 @ 3:46pm
< >
Showing 1-15 of 37 comments
Per page: 1530 50

All Discussions > Bug Reports > Topic Details
Date Posted: Sep 5, 2014 @ 5:10pm
Posts: 37