this post was submitted on 21 May 2025
415 points (98.8% liked)
People Twitter
7500 readers
425 users here now
People tweeting stuff. We allow tweets from anyone.
RULES:
- Mark NSFW content.
- No doxxing people.
- Must be a pic of the tweet or similar. No direct links to the tweet.
- No bullying or international politcs
- Be excellent to each other.
- Provide an archived link to the tweet (or similar) being shown if it's a major figure or a politician.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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
leaks are extremely hard to find and rebooting is just one function call.
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.