steamwebhelper memory leak @ 4.5gigs

[Death_dx]

using constant 1-4 cpu time and the memory usage just keeps going up!
https://i.ibb.co/Z1cxk2d/steamwebhelper-4-5-gigs.png

disabling gpu accelerated rendering seemed to fix it, though maybe valve ought to get some new codemonkeys

[DirtStar21]

why do people not know where the ball is going and how to rotate

[Robert F.]

Someone made a topic about it and made workaround: https://steamcommunity.com/groups/SteamClientBeta/discussions/3/3123786356708994605/#c3123786356710053496
Try removing "What's New" from your Steam Library shelf. I tried it and my steam memory usage goes back to normal as usual,

[Death_dx]

I dont have whats new (nor steam beta) enabled to begin with. So far it's fixed after disabling gpu accelerated rendering as said in op, the option is in steam>interface.

[Death_dx]

not in steam beta

[SleepyKitti ❤]

Some weeks ago, I was playing a game and it was repeatedly crashing and printed a message out of memory. I checked what consumed the memory, this Steamwebhelper used more than 6 GB memory on my system with 80% CPU usage. :(

And it happens completely randomly. Sometimes there are no issues for days, sometimes there are constant crashes.. so it's definitely not normal behavior. It would be great if this issue was finally fixed. This bug has been there since ~December 2020 (at least, that was the first time I ran into it).

[Dr.Shadowds 🐉]

Things you can try.

- Opt into Steam beta, if already in it, opt out instead.

- Clear cache and cookie, then restart client. Steam > settings > web browser > click two buttons to delete cache and cookies.

- Try these settings, see if any improvements on your client for you, then restart Steam, and test.
https://imgur.com/04dWpb7

- Last option, redownloading client files. Head to where you install Steam, go inside Steam folder, delete everything except for Steamapps folder, and steam.exe, once done then run Steam.exe, and see issue resolved.


Things to look into for yourself.
- Ensure not using something that hooks into client causing problems..

- Ensure nothing is causing problems with client, such as anti virus scanner, or whatever other 3rd party apps that trying to interact with client, that it shouldn't be doing.

- Ensure file, and permissions is not being changed by 3rd party app you use, or anything to cause permission issue for the client to function correctly.

[↑↑↓↓←→←→BASelect]

Originally posted by Dr.Shadowds 🐉:

Things you can try.

- Opt into Steam beta, if already in it, opt out instead.

- Clear cache and cookie, then restart client. Steam > settings > web browser > click two buttons to delete cache and cookies.

- Try these settings, see if any improvements on your client for you, then restart Steam, and test.
https://imgur.com/04dWpb7

- Last option, redownloading client files. Head to where you install Steam, go inside Steam folder, delete everything except for Steamapps folder, and steam.exe, once done then run Steam.exe, and see issue resolved.


Things to look into for yourself.
- Ensure not using something that hooks into client causing problems..

- Ensure nothing is causing problems with client, such as anti virus scanner, or whatever other 3rd party apps that trying to interact with client, that it shouldn't be doing.

- Ensure file, and permissions is not being changed by 3rd party app you use, or anything to cause permission issue for the client to function correctly.

Don't forget to keep the userdata folder also some save games gets saved there. Along with your screenshots.

[Forced Descent]

Originally posted by Robert F.:

Someone made a topic about and made workaround: https://steamcommunity.com/groups/SteamClientBeta/discussions/3/3123786356708994605/#c3123786356710053496
Try removing "What's New" from your Steam Library shelf? I tried it and it seems like my steam memory usage goes back to normal as attended,

Can confirm. I've found a youtube video to remove the "what's new" section and the problem was gone. My pc is pretty old and that bs part of the library was making CSGO stutter for weeks.

[Quint the Alligator Snapper]

Another way, which disables all the steamwebhelper.exe processes altogether: use -no-browser as a launch parameter.

This removes all browser-rendered features on Steam, such as the modern Library UI and Friends/Chat UI, but you can use Small Mode instead of the modern Library UI and you'll also automatically get the old Friends/Chat UI. (Why they can revert to old Friends/Chat UI but not old Library UI is an oddity currently without explanation.)

Also, Steam will use less resources, not spawn any steamwebhelper.exe processes, and start up a little faster.

This isn't without drawbacks, though; Small Mode can't uninstall games (need to do that in Big Picture Mode or maybe console), and the old Friends/Chat UI has a few things that make it act buggily with the way chat is currently handled on Steam's server end. Unfortunately it seems Steam is headed in the direction of trying to make everything browser-rendered and less efficient and doesn't seem to want to allow for workarounds.

[Death_dx]

had it happen again, gpu accelerated rendering evidently does nothing, it's just random I guess. I do hibernate my comp a lot I wonder if you guys do as well?

edit: So I restarted steam and that didnt fix it (again) but when I disabled 'hardware video decoding, if supported' that "fixed" it. I guess that since both these settings require steam restart that they reset something that disables whatever is memory leaking. So if you have the memory leak try toggling one of these setting and seeing if it fixes it.

[riddLedSKL]

I disable GPU accelerated and hardware decode options. Still the same. Steam Client Webhelper still uses 2.5gb ram.

[cSg|mc-Hotsauce]

Remove everything in the What's New shelf and test again. Post results.

[Quint the Alligator Snapper]

Does editing the CSS to not show the What's New cause it to not be loaded at all or just hide it? If it causes it not to be loaded at all, that might be another thing worth trying.

[なかの31]

I had an issue like that on my old pc, during the end of last year.

The memory leak was being caused when having the any Chat window opened, and didn't stopped even after closing the chat window.
The issue was less visible if you're using a 64 bits computer. On 32 bits, a few hours with the chat opened could easily take about 2gb of ram, or more.

I don't know if the issue persists, though, beside I didn't had that issue anymore since upgrading the pc.