New Steam Client Using 490 MB's of Memory???

[JockoFlocko]

It's bad enough this thing has to always be running in the background even when I'm not downloading updates or purchasing games, but this release after all the Steam services are added up is now using 522 MB's of system memory in Windows 10.

[( ( < < <🤖> > > ) )]

i'm thinking its a key logger.....
i just played a jigsaw mouse game...
i went from 450mb to 768mb

[black_raen]

Just caught the WebHelper running at 6,482 MB of RAM. Yeah, over 6GB of RAM.

At this point, Steam is just a virus. Going to have to switch it to being a 'run-only-when-absolutely-necessary' program, disable auto-start and write a helper app to auto-kill it when exiting games.

[RiO]

Donitz の投稿を引用：

A framework like React has something like 500 external dependencies.

The react package itself has exactly 1 dependency; on the loose-envify package.
Which in turn has 1 dependency on the js-tokens package.
Which in turn has no further dependencies.

Even if you add something like Redux as a state container; that still has only 10~15 transitive dependencies total.

The problem with React isn't React. The problem with React is with the entire ecosystem that sprung up around it. Filled with a million-and-one examples of just-one-more-abstraction-to-rule-them-all libraries envisioned by astroturf-architects. (Not 'built-by'; oh no. They have their lesser peers for that. Them and the never ending fount of community contributions to lean on.)

The head-spinning amount of idealized ivory-tower architecture that's around and the abject collective apathy for the basic principle of YAGNI ("You Aren't Gonna Need It"); those are what cause the bloat.

[Donitz]

RiO の投稿を引用：

Donitz の投稿を引用：

A framework like React has something like 500 external dependencies.

The react package itself has exactly 1 dependency; on the loose-envify package.
Which in turn has 1 dependency on the js-tokens package.
Which in turn has no further dependencies.

Ah I'm sorry. I must have judged it by the React Native package: https://npm.anvaka.com/#/view/2d/react-native

[Lystent]

TIGGER の投稿を引用：

...Did anyone bother checking ram usage on the old ui before the new one? or are all the complaints just because of people checking ram usage since the new ui?

As someone who has steam on 4 machines, I was able to snag some 'before and after' numbers. This was on my tablet, so things got a little smashed due to the 2 gigs of system ram used for windows, steam, and graphics. I also only grabbed the data just after starting steam up (so this doesn't indicate the result of the usage creep).
Before: 208.1 MB
After: 350.8 MB

[Xaviruso]

Tick-tock の投稿を引用：

Oz Gaming の投稿を引用：

I have 32GB of Ram. The new Steam Client seems to be working nice and smoothly. People with say 8 or only 4GB Ram might find the new client is impacting their system.

Good for you!

That doesn't change the fact that it's an objectively bad performance downgrade, which in software development (and considering that this apparently WAS tested for a decent amount of time in Beta,) is a BAD THING.

So ♥♥♥♥♥♥♥ spot on. Im so sick and tired of seeing people accepting this kind of ♥♥♥♥♥♥♥♥ and even going as far as literally defending this kind of updates. I just love how clueless people are about this ♥♥♥♥, and then they just parrot that you should just get a beefier computer and your problems will be gone. And its like, well, this thing used to be able to run with a minimal amount of resource consumption, now it needs to eat tons of resources but there is no new extra functionality that requires the resources, its simply been modified by patches on top of patches and frameworks on top of frameworks by lazy clueless devs over the years reaching a point where we're consuming tons of resources and dragging a machine down to a halt without adding any useful functionality. Besides, nowadays drawing graphiscs aint even that resource intensive for most hardware that exists, which means the main point of resource consumption is unoptimized webapp trash code. Imagine bring a simple app like steam to the point where its a chromium based crap that eats tons of memory to process the click of a button but cant even remember the previous page you were on, returning you to the library each time something goes wrong....

[Xaviruso]

Donitz の投稿を引用：

Webdev in general has a SERIOUS problem with bloat. A framework like React has something like 500 external dependencies. Not only is that quite insecure (do you really trust the code written by so many people, now and forever?), it also tends to make applications way slower than if they were simply written from scratch. Imagine it like writing an application the same way Frankenstein created his monster.

I think you may enjoy this article: https://tonsky.me/blog/disenchantment/

And then people call John Blow crazy...

We live in a world where most software is trash that was put together by mixing and matching libraries and dependencies like there is no tomorrow and programmers do not understand what is going on under the hood. Nobody likes bothering with looking at what is internally happening anymore, they just want to make software without caring about the performance or even understanding how it works.... because "why waste time reinventing the wheel??" You can always go to stack overflow and copy paste code or use 69 thousand libraries, packages and frameworks.

Its a very sad time we live in where software just gets more and more bloated, slow, unperformant, and all for minimal functionality.

But hey, we cant complain, because web devs will tell you that the framework they are using is "blazingly fast!!!!!" so it must be true!!!

[RiO]

Xaviruso の投稿を引用：

Nobody likes bothering with looking at what is internally happening anymore, they just want to make software without caring about the performance or even understanding how it works

I do bother actually.

And I've shot down inclusion of third-party libraries multitudes of times because I found they were doing this or that in an incorrect way; in an insecure way; in a way that couldn't possibly scale to production throughput requirements; etc. A fair share of "why use this library when platform supports it native?" as well.

Many of my co-workers are equally critical and do their research.
And for many of my peers across the entire industry that will be the same.

!!! --> When they actually get the time to do so <-- !!!

That is the biggest actual problem.
Software complexity has increased due to the scale it is operating on nowadays.
Yet in many software companies management expects similar returns in the same time; or heaven help us: even shorter time "because the tooling is better these days, so you should be able to manage."

The average software product has more moving parts to it than a bridge looping the entire world thrice would have in rivets. Would you ask the engineering crew responsible for putting up a regular-sized canal bridge to be done by sunset; and then have the confidence to send traffic across it?
Because many idiots in management are apparently fine with that notion.


All the frameworks and libraries piled on libraries is just the modern day version of old-skool drag&drop rapid application development. It's a cope by developers to deal with the nonsense management forces on them.
These methodologies in particular prey on junior software developers that haven't developed gut experience yet; and are promised an equal playing field that will 'empower' them to produce at the level of a senior developer with years of experience. Which makes it that more despicable.
Developers who don't know better; who are tricked into adopting snake-oil by astroturf architects that do know better, but care more about their own 'cred' so they'll happily sacrifice entire lines of people to their ego.

[Waldherz]

Steam is using a total of 1.7GB of ram for me now lol.

[g3nsvrv]

Same here, this is my pre and post update resource consumption:

Before Update

Process Name		PID	State	User	Memory (KB)
steam.exe		15896	Running	X	130.220
steamservice.exe	12356	Running	SYSTEM	4.912
steamwebhelper.exe	3148	Running	X	24.008
steamwebhelper.exe	14080	Running	X	2.732
steamwebhelper.exe	10784	Running	X	17.580
steamwebhelper.exe	2752	Running	X	13.516
steamwebhelper.exe	17380	Running	X	140.484
steamwebhelper.exe	11540	Running	X	82720
steamwebhelper.exe	20452	Running	X	9.800
steamwebhelper.exe	16616	Running	X	24.080
					TOTAL	450.052

After Update

Process Name		PID	State	User	Memory (KB)
steam.exe		13700	Running	X	52.008
steamservice.exe	1544	Running	SYSTEM	5.688
steamwebhelper.exe	22320	Running	X	31.156
steamwebhelper.exe	15408	Running	X	360.408
steamwebhelper.exe	17080	Running	X	2.700
steamwebhelper.exe	16392	Running	X	122.380
steamwebhelper.exe	12756	Running	X	10.564
steamwebhelper.exe	8888	Running	X	31.680
					TOTAL	616.584

The new GUI is great, but at what cost...

[D!ablou]

I'm a 4GB survivor, this is hell now.

[Fearagen]

D!ablou の投稿を引用：

I'm a 4GB survivor, this is hell now.

Hell, ignoring the potential memory leak in steam, 4gb for even Windows 10 in 2023 is basically near unusable, open a browser with a couple of tabs and there goes some of the memory, probably not an enough to run a game and listen to music at the same time.

[A Simp Named Slickback]

I really hope Valve works on the RAM usage of new Steam. This should be like half of what it currently is, which on my computer after having been open for a while it is nearly 1 GiB. I like the new steam but... come on. All this Chromium Embedded Framework stuff is absurd.

[Tiberius]

This update is horrible. Home button sometimes doesnt work and often times bring me to the last page i visited.

I mentioned chrome integration is the worst thing they did to steam mobile, now they also bring that sht to the desktop app

[IcedLance]

Mine's using 1.2Gb currently and if I leave some game running overnight (i sometimes forget to close them), the overlay process gets inflated to 4-6Gb.

The recent GUI update certainly needs a lot of work.