安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
Windows 10 last version, cleared cache, re-installed Steam, disabled GPU accelerated, etc...
Nothing work.
But not for Steam !
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
Maybe last update from Windows 10 ?
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
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.
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
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.
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.
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.