Ungstein 2020 年 10 月 19 日 上午 12:21
BUG: Memory Leak - "steamwebhelper.exe" Using 5.5 GB RAM
Edit: When I killed the offending process, the Library page went blank briefly before reappearing.

I realise this has been posted many times before but I would like to amplify the message as nothing has been done about it. Steam is turning into a bloated piece of "code"; the CEF process (steamwebhelper.exe) is currently using 5.5 GB of memory in a single process. Previous discussions seem to have isolated the leak to the Library, which seems accurate, as when I kill the process, the chat window stays open. I like to leave Steam open in the background, which I have done for over a decade. At this point I'd rather have embedded Internet Explorer instead of this crap. Could somebody from Valve please acknowledge this problem and provide a workaround at least. Hate to sound like a Karen but this really is unacceptable for an application that should have a minimal resource footprint.

OS: Windows 7 x64
Beta client is disabled.

If more information is required, please ask.
最後修改者:Ungstein; 2020 年 10 月 19 日 上午 12:41
The library went blank because it's a web-rendered page. The new Steam Library uses web-rendered pages for everything, even though it really shouldn't because it doesn't need to (the old one didn't need to do this).

OP, I suggest you use the -no-browser launch parameter. I'm using it too. Just turn your Steam shortcut from:
C:\installpath\Steam\Steam.exe
into:
C:\installpath\Steam\Steam.exe -no-browser
(If you have Steam set to start up on system start, then you'll need to find the startup process and edit that.)

This will break the Library as you see it, but you'll still have access to Small Mode, which is a list of all your games (and has the advantage of being keyboard navigable). Also you'll get the old Friends chat UI.
You won't be able to use Steam as a browser, not surprisingly. But you will have a Steam that launches with NO steamwebhelper.exe processes, which means it'll actually take less system resources AND launch faster.

If you need to use the Steam website, I strongly suggest using a standalone browser anyway; Steam's built-in browser is (still) missing a variety of features, such as keeping history, which is needed to find where the threads you posted in went, if they got moved, since the Steam notification page only says "moved or deleted".

(Furthermore, using your own standalone browser will let you realize that "sign in through Steam" shouldn't require actually putting in your login info, meaning that you'll learn that "sign in through Steam" pages that do ask you for that are phishing.)

Just be careful that you don't try to uninstall games through Small Mode. The uninstall confirmation prompt is also a web-rendered page (you see how silly this is now?) and since it can't be displayed, it will cause the uninstall to hang until you restart Steam. If you're using -no-browser, you need to go into Big Picture Mode to uninstall games.



...and, when you step back and look at this you realize just how silly it all is to have a mandatory game launcher that forces you to deal with this nonsense.
< >
目前顯示第 31-45 則留言,共 49
Crowzer 2020 年 10 月 20 日 上午 3:10 
I'm in the same situation :

Windows 10 last version, cleared cache, re-installed Steam, disabled GPU accelerated, etc...
Nothing work.
m4dEngi 2020 年 10 月 20 日 上午 3:53 
引用自 Crowzer
I'm in the same situation :

Windows 10 last version, cleared cache, re-installed Steam, disabled GPU accelerated, etc...
Nothing work.
You obviously forgot to reinstall windows.
Ungstein 2020 年 10 月 20 日 上午 3:57 
@Jonius7: I wish I could help but I am no programmer. Honestly I don't think it's worth the effort of injecting custom JS when a single update will most likely break it. I went through that pain when I made Steam skins in 2013...
Crowzer 2020 年 10 月 20 日 上午 3:59 
引用自 m4dEngi
引用自 Crowzer
I'm in the same situation :

Windows 10 last version, cleared cache, re-installed Steam, disabled GPU accelerated, etc...
Nothing work.
You obviously forgot to reinstall windows.
I did it, for real :D
But not for Steam !
最後修改者:Crowzer; 2020 年 10 月 20 日 上午 3:59
Jonius7 2020 年 10 月 20 日 上午 5:16 
引用自 Ungstein
@Jonius7: I wish I could help but I am no programmer. Honestly I don't think it's worth the effort of injecting custom JS when a single update will most likely break it. I went through that pain when I made Steam skins in 2013...

There is a question of maintainability. My JS tweaks have been fairly simple up to this point, but when the Steam Client update on Oct 8 rolled around, I had to update half my tweaks because the variable names changed. This doesn't seem to happen often though (every 3-5 months?), if it did, or I had many more tweaks, I would probably make another Python script that could "wildcard" these variable names.

There are my current set of published Library UI tweaks: https://github.com/Jonius7/SteamUI-OldGlory
最後修改者:Jonius7; 2020 年 10 月 20 日 上午 5:17
Black Blade 2020 年 10 月 20 日 上午 5:17 
引用自 Crowzer
I did it, for real :D
But not for Steam !
And the issue comes back even after reinstalling windows? in that case maybe its some type of hardware parts that is clashing there...
Crowzer 2020 年 10 月 20 日 上午 5:20 
Yes. I really don't know what it causes this issue. I end up to close Steam while I don't play any Steam games. My hardware is new : AMD 3800X, MSI X570 and 2080Ti.
Maybe last update from Windows 10 ?
m4dEngi 2020 年 10 月 20 日 上午 5:53 
引用自 Black Blade
引用自 Crowzer
I did it, for real :D
But not for Steam !
And the issue comes back even after reinstalling windows? in that case maybe its some type of hardware parts that is clashing there...
Yeah, you forgot cosmic radiation! Could be anything except bugs in Steam UI code.
Black Blade 2020 年 10 月 20 日 上午 6:00 
引用自 m4dEngi
Yeah, you forgot cosmic radiation! Could be anything except bugs in Steam UI code.
Mate, can you get over it?
I am not saying it's not an issue with Steam, I am saying that as not everyone has it its not only Steam that is creating the issue but has something else that is also in play here that make it happen most likely
If we can find something shared in the matter Valve can try to fix it on there end or can try to solve it our self or we can contact whatever may be involved

Just going "Valve fix" is not likely to give many results even more if Valve can't recreate the issue, I mostly want to try and find where the issue rise and what is shared to everyone that has it so maybe Valve or us can find and solve it
m4dEngi 2020 年 10 月 20 日 上午 7:04 
引用自 Black Blade
引用自 m4dEngi
Yeah, you forgot cosmic radiation! Could be anything except bugs in Steam UI code.
Mate, can you get over it?
Maybe some day i will.

https://steamcommunity.com/groups/SteamClientBeta/discussions/search/?q=memory+leak&gidforum=1694923613875237366&include_deleted=true&sort=time

Memory leaks were reported and discussed since early beta release. And nothing was really done about 'em since then.
Black Blade 2020 年 10 月 20 日 上午 7:17 
引用自 m4dEngi
Maybe some day i will.

https://steamcommunity.com/groups/SteamClientBeta/discussions/search/?q=memory+leak&gidforum=1694923613875237366&include_deleted=true&sort=time

Memory leaks were reported and discussed since early beta release. And nothing was really done about 'em since then.
At least in one of them:
https://steamcommunity.com/groups/SteamClientBeta/discussions/3/1742226629856743743/

Valve reply and try to find it, found out it was something else that had the issue from what it seems
I disagree with the idea that nothing done about it, it's possible they just have not found a fix yet

Some of the topics in the search compline about just 202MB and the like

It's happening its possible the question is why, and if its possible to solve it
RedLightning 2020 年 10 月 20 日 下午 12:47 
They could have *solved* 100 percent of these issues if they just didn't totally muck up the client in the first place.

Why they gotta do what they do is beyond me.. then they don't even bother to fix issues with the *new* client in a timely manner. I still feel like my games in SteamVR took a major hit since the updates to the client started.

Sucks too that everyone is stuck on the same train where updates break games and the client.. an there is zero recourse..

Don't even know if Valve are listening.. I do know that a bunch of yes men are listening all the time for sure, however.

Never saw the leak complaints about the new (old) included cromium initiative before the new client. .. . and how long has this been out .. still as sluggish as ever..

I remember when I could just use the client without worry about all these resource hungry performance degrading things that the *new* Steam client do.
SeriousCCIE 2020 年 10 月 20 日 下午 3:06 
I've noticed that less capable hardware that I have the Steam client installed on (some pretty ancient machines, some modernish, and one with the same processor and memory amount but a 7 year old video card as a sort of plan-B system for when the primary one inevitably betrays me and refuses to run)...

Steam's client seems to use different amounts of memory depending on the system and what it can effectively lock up for itself.

Ultimately it seems that (in my modest testing), if I gimp the system or make it look crippled, steam behaves better. Setting it all to low bandwidth mode or even applying QoS to force a low speed connection (as opposed to just stating I have a low speed connection) can help.

I found that if I didn't consume the available memory before loading steam, steam will happily swell its memory footprint via preloading whatever-- even if I do not do anything more than load steam-open collection avoiding library "home page" entirely--launch game. But, if I do consume the memory and leave just a little left, Steam fits the space I provided it and then I can exit whatever program and launch the game I want before Steam wisens up to my tricks. If I click around and leave that memory available for too long, it seems to take notice that I might be interested in seeing more stuff I can't block.


Ungstein 2020 年 10 月 20 日 下午 7:53 
@SeriousCCIE: I was able to use this method to prevent Chrome from using *all of the RAM* about 5 years go. I found a better method in not using Chrome. It seems to me that CEF is treating the tabs in Steam (STORE, LIBRARY, COMMUNITY, etc.) as Chromium browser tabs, so they each get their own steamwebhelper.exe process. Friends also gets its own process. Multi-process is part of the reason for heavy RAM usage, but ultimately I think it comes down to poor optimisation based on trying to convert a native Windows application into a "platform agnostic" web version. I can only assume this is part of the push to Linux, with the irony being that most Linux users would resent the new interface changes on the principle of software freedom (myself included).

p.s. I realise that Steam is proprietary software, I am using the term "software freedom" in the sense of being able to choose between difference interfaces.
no pego nada 2021 年 5 月 13 日 下午 12:15 
引用自 Ungstein
Thanks for the suggestions. I already have those settings enabled but it didn't help. Could be a Win7 thing but I think it's a bit of a cop-out to jump to that immediately. Hopefully there are some Win10 users out there with the same problem.
I have the same problem and I use Windows 10 20h2, Ryzen 3700x and 16 GB Ram 3200mhz, the Steam Client WebHelper process uses between 3 or 4 GB of ram, but it only does after a couple of hours of being open Steam. I detected this problem 2 weeks ago it had never happened to me.
< >
目前顯示第 31-45 則留言,共 49
每頁顯示: 1530 50

張貼日期: 2020 年 10 月 19 日 上午 12:21
回覆: 49