Nice, an operating system that kills desktop X apps when they exceed 500MB and no mention in the install docs.
#OpenBSD
...you can get the system into a state where it would take weeks to successfully login & kill whatever allocated so much.
-
-
Yes, I've been in such situations. They aren't cool. What's suggested on Linux to do on malloc failure? In games it's easy, you often have a
-
Library level - back out the operation and return an error (you did remember not to commit/free anything before finishing alloc, right?).
-
Application level - depends on the app. Those with no valuable data of any sort can just try to show an error and exit...
-
But if you have any data the user might be upset to lose, you need at least an allocation-free emergency-save/recovery-dump code path.
-
Or you need to ensure that data is constantly saved in a form suitable for recovery after abort (see browsers' tab-restore features).
End of conversation
New conversation -
-
-
have wished before that Win64 could autokill / fail-to-alloc to processes which try to allocate excessive amounts of memory...
-
#openBSD /etc/login.conf configures that type of behaviour. -
yeah, but an issue is 64-bit apps in Windows 10; end up sometimes needing to use a specialized malloc to fail or die past a certain limit.
-
I use windows a fair bit but I don't program it or know its oddities.
-
main issue is, a 64-bit program with a bad leak may quickly eat GBs of RAM, leading to thrashing, and possibly a BSOD.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.