As it turns out, this wasn't a memory leak at all. I decided to see if I could max sexpbot's memory out by reloading. I got it to rise around 20-30 megs and then it stabilized and eventually jumped down 10 megs and didn't rise again (gave up 10 reloads later). I don't know how this stuff works, but I suppose maybe the memory just remained reserved or something. GCing does absolutely nothing. For a smaller- scale test, you can just try requiring clojure.java.io or some other namespace about 100-500 times and watch memory while doing so. It'll grow pretty substantially.
Anyway, it's doesn't appear to be a real problem at all. -- 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
