Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
Malware is not the right word, that destroys your pc.
It's more like bloatware like how windows 10 is.
malware 10? that malware microsoft forced on users back during release, that messed up tons of pc's including businesses?
Steam is configured to start when PC starts. Steam Client Webhelper starts at small RAM usage, but gradually builds up, even if I never actually open Steam from System Tray or play any games from it.
Note that this memory leak did not exist prior to the new interface upgrade, so it's safe to assume this has something to do with the software infrastructure supporting this new interface.
Steam Client Webhelper process memory usage is increasing by between 0.2 and 0.7 MB per minute, constantly, until I open Task Manager and end the process.
It is also worth noticing that while that happens, there are TWO "Steam Client Webhelper" processes in Task Manager, one with the memory leak and another being stable.
Ending the leaky process seems to have NO effect on Steam functionality, therefore I will make another assumption and say that, since there are two processes and the leaky one has no effect on Steam when killed, it could be an orphaned process which Steam fails to kill, and it keeps growing by itself for one of many possible reasons.
The only workaround is to keep an eye on memory usage and kill the process in Task Manager when you see it eating RAM.
ehhh
there is
they did push it on a lot of us and it did cause a lot of problems
the most notable was the lady that sued ms for the forced update and got 10g's for the losses
i got hit with the x not meaning close that she did and it jacked my pc
proof of something known worldwide? lawsuits over broken pc's, lost data and lost money for lots of businesses?
google if you for some odd reason is the first you have heard of it...
seeing as it was back when win 10 got pushed in important updates back when win 10 released, then auto updated tons of pc's to win 10, which back then had horrible issues with installing and could wipe your drive, "incompatible hardware", ect..
anywho, we all know why you quoted me and sadly its not working like you would want.
no clue why you got an answer to why you quoted me?
ok... you do you and be on about nothing.
ms was pretty shady in the way they pushed 10 when it was first being released
it seemed like every week we were seeing another article about a kb that was adding nagware
or something new to get people onto 10
even going so far as to put one in a security update
that was in '15/'16, though
and them calling it malware is a bit dramatic