Nice, an operating system that kills desktop X apps when they exceed 500MB and no mention in the install docs.
#OpenBSD
-
-
Replying to @Sonophoto @blakkheim
#OpenBSD doesn’t kill anything. Low ulimit just means the allocation fails. It’s Firefox that then tries to use invalid memory, and crashes.2 replies 0 retweets 2 likes -
Same problem shows up on Linux if you turn off memory overcommit. https://www.etalabs.net/overcommit.html (h/t
@RichFelker)3 replies 0 retweets 2 likes -
Replying to @AnthonyJBentley @Sonophoto and
There are two unforgivable users of malloc: programs that don’t check the return value, and libraries that kill the program if returns NULL.
3 replies 3 retweets 3 likes -
Replying to @AnthonyJBentley @Sonophoto and
virtual memory be available?
2 replies 0 retweets 0 likes -
Replying to @ArvidGerstmann @AnthonyJBentley and
Nope, that is the issue with
#OpenBSD. /etc/login.conf has limits on mem avail to processes for security. Memory is not infinite.2 replies 0 retweets 1 like -
Replying to @Sonophoto @ArvidGerstmann and
Yes, configured resource limits are a very good idea to keep abusive processes from making other processes OOM or swapping box to hell.
1 reply 1 retweet 1 like
(Firefox is a prime example of such an abusive process that keeps alloc'ing memory as if all system resources belong to it.)
-
-
Replying to @RichFelker @ArvidGerstmann and
haha! I just realized who you are. Thanks for
#musl! We didn't end up using it but we did test with it. Its still on my mind ;-)0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.