Hacker News new | past | comments | ask | show | jobs | submit login

  > you need to run it in it's own process
Assuming that you can detect OOM in userspace at all, which usually isn't the case on Linux (or any other system with overcommit).



huh? you'd notice your child process was exited with SIGABRT.


SIGABRT doesn't necessarily mean OOM, and in any case if you're prepared to monitor child processes for aborts then you'll be perfectly fine with the fact that Rust's default stdlib aborts on OOM, which is the context of this thread.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: