>> Running in VisualVM suggests that % of Used Heap is actually very >> less. So the problem is that GC isn't running often enough, so the JVM >> has to keep allocating more memory.
By problem I meant, in my case, of too much memory consumption. > Odd. I'd expect the JVM to run a GC immediately before reporting that > the heap has been exhausted. That certainly is odd, I would expect the same. But quick googling doesn't turn up any references of the JVM which mention this. Can you take a heap dump of the chunked and non-chunked versions (-XX:- HeapDumpOnOutOfMemoryError)? -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
