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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
Why does Chrome do that? And which browser doesn't?
And it is still fast? It's kinda hard to believe that that ram isn't actually used (well).
https://www.youtube.com/watch?v=y0FLiCcXS4s
what do you think ReBoot are these test valid...
I got tired of it eating ram I need for other things when it was doing nothing, and just threw in a script to find and kill the steamwebhelper child/sub processes ever 45 minutes, it helped a bit.
steam has become just another one of those awful, bloated, thrown together apps that eat ram like it's infinitely available and seems to require a regular full wipedown to work properly.
problem with "users have plenty of ram" mentality is that when everyone thinks this way, a handful of apps can eat 32 gigs sitting idle. sorry guys, i need that stuff for something useful, and you should learn to code properly.
https://github.com/lowleveldesign/process-governor
Keep in mind that applications are not written with restrictions in mind and thus can become unstable.