Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
Today I noticed that Steam.exe on my computer was occupying one whole CPU core as well constantly. Switching to Big Picture mode and back did not fix it for me, neither did enabling Push-To-Talk as someone had suggested. Process Explorer showed that the main thread of Steam.exe was hogging all the CPU for whatever reason.
What worked for me was switching the Library view from the Full Details view to one of the other views (list, icons) and back. Steam.exe is happily using ~0% afterwards when idle, which is how it should be.
There are 2 process threads that keep blindly banging away at the CPU (albeit, only consuming less than 1.5% of my fast 4.4Ghz multicore CPU) when Steam is idle. This activity appears to be "by design". Anyway, now, Steam consistently uses 0% CPU (when I'm not using the Steam app). Steam will still process updates on startup. The suspended threads will go active only when they're actually needed.
Since Its pretty clear to me that Steam developers intended for Steam to work this way; I will NOT be posting the actual code to do this. I would rather stay in good standing with Steam and Steam community. :) ...just know, there's a programmatic automated solution for this.
did worked for me too. But only till next steam restart. After that I need to do it again.