Colin Jones <trptco...@gmail.com> writes: Hi Colin,
> Right, this is because nREPL uses clojure.main/repl each time it does > an evaluation. See http://dev.clojure.org/jira/browse/NREPL-31 for a > related issue that was addressed by modifying clojure.main/repl. > > I'm not sure where a fix for this would belong (nREPL or > clojure.main), but I went ahead and opened an nREPL JIRA issue to > track it: http://dev.clojure.org/jira/browse/NREPL-36 Some time ago, I was also astonished by the large number of class loaders. But I'm pretty sure that the class loader list (i.e., ClassLoader.parent -> ClassLoader.parent -> ...) didn't grow without bounds, but sometimes a parent becomes set to null and the previously referenced class loader and all its parents becomes garbage collected. I didn't do any debugging, but just used a function similar to Vladimir's `print-class-loader-stack` every once in a while. Bye, Tassilo -- 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
