2017-03-08 9:00 GMT+01:00 JokkeB <[email protected]>: > Now tracking down if I'm simply too low on memory or if the app has a > memory leak, but that's a different topic. >
Your app may well be fine. The OOM killer removes processes in descending order of memory usage, when RAM runs out. As java processes are usually large, those are amongst the first victims. This happens even when your app has plenty of free heap, because the java garbage collector reserves a lot of memory before allocating it, and you only get OutOfMemoryExceptions, when the GC hits its limit (set by -Xmx). To fix the OOM killer issue, simply add more swap space. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
