On Tue, Dec 01, 2009 at 08:16:41PM -0800, rzeze...@gmail.com wrote: >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.
I actually found the problem by doing a heap dump and just using jhat. It was very obvious that there were way too many LazySeq's around, so I just picked one randomly, and asked to see the roots that lead there. It pointed right back to a local variable in my function. A little bit of disassembly of the bytecode, and it was clear what was going on. David -- 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
