4 ms·
Out of memory errors are extremely dangerous in concurrent code. It is one of the few ways that will leave things in an inconsistent state as it releases the mo
by spullara 5y ago
Out of memory errors are extremely dangerous in concurrent code. It is one of the few ways that will leave things in an inconsistent state as it releases the monitors and you likely aren't catching them and fixing things up. I highly recommend all Java production JVMs have one of these set:
-XX:+ExitOnOutOfMemoryError
-XX:+CrashOnOutOfMemoryError
- pram 5y agoAgree! OOM errors also leave a lot of things in weird states where they're functionally dead, but the process is still running. So depending on your monitoring everything looks 'normal'