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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
also are you using steam client stable, or beta?
This bug is fixed in the Steam client beta, and it should roll out to everyone probably fairly soon; we're already overdue for a public client update, as they're usually released approximately monthly and the last one was March 7th.
Stable client.
If the file size is 22kb , so the issue not comming from here i guess.
Have you try to clean the steam cache ? This feature can be done under the steeam setup paraméters.
If you still have problem after that, may be you can try to use steam://flushconfig like it's been explained here
https://appuals.com/how-to-use-steamflushconfig/
But in general, I'm waiting for a patch from Valve.
302 ko seems a bit too heavy to me. Just delete the file while steam does not run , the file will be rebuild soon after.
What have you done exactly ? checked the file size of using steam-flush ?
Have you cleared the cache too ?
It's so stable that it eats all of your RAM.
Weird...
Can you post a screenshot done under taskmanager plz?
https://postimages.org/