Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I noticed that the memory usage just keeps rising, it is much lower when you launch the game. I have plenty of RAM, but when the game reaches 2.5GB RAM it becomes unplayable.
What distro are you running? AMD or Nvidia graphics card?
Nvidia GTX 480
Thanks for the reply.
I'm using Fedora 21, but I can confirm that this issue affects OpenSUSE 13.2 as well. I'm also using a Nvidia graphics card.
I sent a message to Valve a few days ago, I hope they fix this.
You and me. Problem is that this occurs more the longer you play. So by round 12-13 when your team needs you most I end up disconnecting to fix the memory leak. Also have to restart as simply reconnecting does not fix it.
Also what really sucks is that upon reconnection you have considered to committed "suicide" and get no money? really messed up.
But overall i am super greatful valve brought this game to linux. I really hope it becomes optimized better however.
To me it happens anytime after 80 minutes of gameplay. I don't get disconnected, but the game becomes unplayable, pretty much slow motion.
I'm also grateful that Valve ported CS:GO to Linux, but they need to fix a few things, like V-Sync, which is broken.
http://blog.counter-strike.net/index.php/2014/12/11061/
i have been playing post update and still experiencing the problem so i dont think its fixed. but i will give your solution a shot and try to do single core rendering
The update didn't fix the issue.
Disabling multicore rendering worked for you?