- Oct 20, 2019
- 907
- 639
You mean with the 2.02 patch fix this shouldn't happen anymore? Or should I get worried? I use a potato pc after all.
My laptop here is likely over 7 yrs old at this point. Granted, it was top of the line in the gaming space at that point, but still ... ancient by today's standards.Even with a beaf PC, you will get this problem (if that's not something that come from my own computer), because it's simply the game not clearing his own memory making it unstable at some point. And WolfRPG (and other RPGMaker like thing) have limited ram allocation, like everything else on a computer, if it exceed it, you get problem and crash.
I played the game, including it's DLC mostly through to the end and didn't experience any issues.
Haven't quite monitored RAM usage on the game while playing, but just in general, strictly spouting technical mumbo jumbo ... there IS a hard limit of about 2GB on any 32bit process (in WinOS). If they're using a 64bit build of the engine (e.g. the game's exe is a 64bit process) ... then no, you do NOT have such low limits.
Now, sure ... any process with a serious enough memory leak can saturate the available resources, be it memory or available threads or whatever, and even crash due to an OutOfMemoryException/StackOverflowException or whatever else.
But for it to die of an OutOfMemoryException it'd have to be a real serious, consistent issue AND/OR you'd need to only have access to a very limited amount of RAM in your PC so that it fills up before it has time to clean it up (e.g. below the minimum/recommended spec).
Now, I also played this game for many hours straight when I went through it, but I didn't see any crashes due to memory leaks of some sort.