安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
此主题已被锁定 
讨论规则及指引
举报此帖
its that simple... make it happen..
Yes, though it's really better to leave that to the OS. Steam should simply not have memory problems at all, that's their part of the job. Resource limits are best left an OS level responsibility, so that no program/process/app can eat up all of everything, and is restricted in terms of what resources it's allowed to access.
Funny thing is, Linux already has a fully functional interface for this, to put limits on everything from RAM to CPU, disk usage, file access, network, I/O and a lot of other stuff (the cgroups system, primarily).
It's just that nobody seems to want to enable this by default. Most Linux distros (and Windows, last I checked) will happily allow you to do things like:
-fork bomb, spawn a million processes spawning a million more - freezes the system almost instantly. It just takes one bad program with a bug and it's technically allowed to freeze your entire system.
-consume all available ram, nothing left for anything else.
-bombard the disk and use up all available space (that cripples pretty much any windows or linux).
People have brought this up in windows and linux forums many times. Responses are often in the line of:
"But if you put default limits on how much ram it can use, what if a process needs all that ram?" (yeah, how often does that happen compared to the contrary problem?)
"It's hard to do because we don't know which programs need access to what" (yes, it's work, but someone's gotta do it at some point - perhaps software could come with a little manifest of what it needs, just like phone apps do).
Unfortunately, steam implementing limits etc. on its own would quickly become a bandaid - it shouldn't have to have these because it should be done right in the first place.
I've started launching steam (on Linux) with an enforced memory limit. If it eats all the ram I gave it and crashes - fine. Better crash after gobbling up 4-8gb than letting it eat all my ram and then crash.
sending this feedback to them... LOL
memory leaking from Steam Client WebHelper program
the program has 7 instances and one of those instances is leaking or using more and more ram the longer the program is running and it doesnt release ram when you open up other different programs like art and video software which require a good portion of ram to function smoothly.
hahaha. This might actually be useful, I wouldn't be surprised if they actually act on these reports to a degree, or gather stats, so if a bunch of users report the app, it's possible ms might send a nudge valve's way to tell them "take it from us - you have a problem".
<insert "Why not both?" gif here>
:P
Also why local screenshot need be an internet to see them?
thats good... it will be interesting...
its probably like this at the window office...
https://www.youtube.com/watch?v=FXMcbhn6Np0
https://superuser.com/questions/1239257/how-do-i-limit-ram-consumption-of-a-particular-executable
https://stackoverflow.com/questions/192876/set-windows-process-or-user-memory-limit
I'm not on windows any more so I can't try it myself.
On Linux it's just (repeating it here for completion):
systemd-run --scope -p MemoryLimit=4000M steam
..to cap it at 4GB.
I have enough ram but if i was to shutdown
steam every 12 hours it wouldnt go over 750mb
so that sort of tells me anything over that is not needed at all....
4GB naaaaaaaaaaaaah
Set it to whatever you like. I just recommended 4 as a baseline so it won't sputter and die within the hour. A few gigs is enough to keep it managed, but alive for long enough that you get to do stuff and restart before it crashes.
Try 750mb if you want - I made it crash within a minute when I set it to 500MB yesterday, so you may face some issues. Setting it to eg. 1200 mb and then using steam for a while is probably a decent way to test if you have the memory bleed issue, as it should choke and die pretty quickly from that (but still have enough ram to begin with that "this should have been enough.. you screwed up steam" is a fair statement).