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
No sensible developer is going to officially support an operating system that's been discontinued for years at this point - even if the game TECHNICALLY might run. It's just way too much support and programming work.
I'm sorry to say that all those steps you took to fix it and the time you wasted were for nothing.
In fact, everybody has this issue and it is not OS-caused. It has been mentioned numerous times that this is a Unity (the game's engine) issue that requires upstream updates from Unity themselves and many have pointed out fearfully that this fix might not ever come.
The only band-aid fix you can apply to make it less painful is to get more RAM. For instance I'm at 8 gigs and I definitely feel the leak after an hour but a friend of mine is at 16 and he almost never restarts, also probably helped by the fact that at most he played for 5-6 hours per session.
You can also free up existing RAM that's used for other processes but that will only minimally impact it. I suspect this is what caused you to believe you fixed it since there was more RAM to consume for the application after a fresh install.
Normally when data is no longer needed applications run multiple ways of clearing it from RAM so that space can be made for other data that needs loading. Memory leaks are caused by poor memory handling.
When a leak happens old data is left stored in RAM even though it is no longer needed by the app. That old data slowly starts clogging RAM, consuming more and more until it reaches the RAM capacity limit. That is why a restart fixes the problem since if the application consuming all that RAM stops executing, the RAM allocated to it is also freed of stored data.
This is just a basic explanation and I suspect Unity's memory leak actually does clean out old data but at a very poor/slow/inefficient rate, which is why we're not seeing a complete freeze of the game (and your system) eventually like with the more basic memory leaks.
X to Doubt. OS vulnerabilities are for elevating privileges and easier spread within a local network(Local because your router blocks incoming traffic by default). They are not the attack vectors. The attack vector is generally getting someone to download a malicious file, by that point its already on your system, doesn't matter what OS you have. You don't need admin rights to do damage or even connect to the internet to send any information you want back.
In a Business you can argue its a lot more valuable because you have hundreds of people who are not bright and will click on obvious fake e-mails and download and run the attachments, so your doing it for damage mitigation. But for a home PC which only you use its not an issue (Most people don't have multiple computers on their home network).
What you need to keep up to date is stuff like your Browser, applications which face the internet. Once its on your PC its already too late.
Not all Unity games have this issue, so are we sure its actually one of Unity's systems which is leaking and not how the game is using them?
Thats actually false. Its only an issue if the exe uses Windows API functions which are not in an older version of Windows(Which is highly unlikely). Even if they do its very easy to have fallback functions in place which do the same job but for older systems.
The only thing they really need to do is have 1 PC which has Windows 7/8 Installed and see if it runs.
Windows 7, 8, 10 and 11 are all based on the same architecture. They are not re-inventing the wheel here, its just incremental differences.