4 ms·
I don't know what kinds of things you're doing on the JVM, but the only situations where I've seen these kinds of errors were either a) batch jobs on massive am
by Tainnor 5y ago
I don't know what kinds of things you're doing on the JVM, but the only situations where I've seen these kinds of errors were either a) batch jobs on massive amounts of data (which yeah... it figures that they could OOM, not sure how you'd prevent that), or b) a serious error in application logic.
In general, I don't really encounter these problems and neither do most other people who write for the JVM.
- pjmlp 5y agoSame here, usually you get that from code that uses new everywhere without any kind of thought regarding proper use of algorithms and data structures.