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
What you describe is what we refer to as a memory leak. Instead of releasing memory back to the system that is no longer needed, the program just allocates more. Over a long enough timeline, the program will consume every available byte locking up the computer.
It's a bug in many applications, not solely a game related one. It rarely appears these days but is still possible given the right circumstances.
I'm playing an older game from 2017 and I believe some other games were somewhat oldies too. I believe the one I keep thinking of that happened the most was turn based, but I could be very wrong. Turns would take significantly longer to process the longer the game ran.