Fixing a memory leak takes essentially looking at random data that got there somehow and try to figure out the source. You know what approximately it is by analysing a memory dump but it’s most likely a common structure that is all over the app. Best case it’s easy worst case it’s looking for a needle in a haystack.
On the other hand, checking if memory is blowing up, then using already built save and load functions is pretty straight forward. Especially since Elder Scrolls saves the entire state and reloads it.
I still can’t fathom how implementing that “solution” is easier than fixing a memory leak. Like what the hell?
Deadlines have entered the chat.
shareholders have entered chat
Fixing memory leaks (while not breaking anything else) is surprisingly difficult sometimes.
Fixing a memory leak takes essentially looking at random data that got there somehow and try to figure out the source. You know what approximately it is by analysing a memory dump but it’s most likely a common structure that is all over the app. Best case it’s easy worst case it’s looking for a needle in a haystack.
On the other hand, checking if memory is blowing up, then using already built save and load functions is pretty straight forward. Especially since Elder Scrolls saves the entire state and reloads it.
leaks are extremely hard to find and rebooting is just one function call.