I'm having similar problems, but am hesitant to post until I do some further analysis.
However, I thought I'd share some techniques I'm trying to use to hunt down my memory leak. First, you can make GC verbose. -verbose:gc For even more detail, add the following. -XX:+PrintGCTimeStamps -XX:+PrintGCDetails. Second, do a heap dump. If you are using Java 6 then you can use the jmap tool. jmap -dump:live,format=b,file=foo.hprof <PID> Once you have the heap dump you can use the Eclipse Memory Analyzer Tool. It can take your heap dump and create various reports. One of them being a "dominator tree" which will show you what object has the largest retained heap size. I'm still a complete novice with it, but it already helped me track down some memory leaks at work. Check out this article, goes over what I just said and much more. http://olex.openlogic.com/wazi/2009/how-to-fix-memory-leaks-in-java/ . -- 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
