I did start with visualvm. I posted a screenshot in an earlier thread. However I'm unable to make sense of its output. jhat pointed straight to the closure with the reference. visualvm gave me a thousand cascading widgets to expand with names that were meaningless to me, none of which pointed back to the closure. I'm looking at it again now, trying to find another leak. The references for a char[] start at "String" and go back to "cache (Java frame)", with no symbol anywhere that I can relate to the program being run. I don't know what to do with this. The Strings are from another seq: lines from a file via line-seq.
Unfortunately, jhat just hangs on this object, so I have no working instrumentation. On Wednesday, September 11, 2013 1:08:33 AM UTC-7, David Powell wrote: > > jvisualvm has an innocuous button called "Dump Memory" or something. > You'd expect it to write out a core dump or something, but actually it > opens up a GUI which lets you interactively explore all of the objects on > the heap. It is pretty amazing. Much better than jhat, which I've found > to be really flakey. > > Good for finding Classloader leaks too, or just generally finding where > all your memory has gone via the Compute Retained Sizes option. > -- -- 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 --- 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 clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
