-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leaks #3
Comments
I'm seeing this as well. Unfortunately, I'm not deep enough into classloaders or profilers to get much further than the few hours of digging through jvisualvm I did, to no avail. Unfortunately, apply @tcrawley's clojure patch doesn't solve it for me. The second example above takes ~10 iterations to run me out of PermGen space. Sorry I don't have more insight here. |
If someone can create and share a simple app that recreates this, I'd be happy to take a look and see if I can figure out what's retaining the reference to the classloader. And if it's a flaw in Clojure, I'll see about adding it to CLJ-1125. |
Whoops, got your other GH username @tobias :) Good news: in my newly trimmed-down use case, your clojure patch is looking great, so it must be something higher up than classlojure in my original use case that was retaining the references. Thanks! |
No worries, I'm squatting @tcrawley to catch the confusion between my nick-everywhere-else and here, so it worked! If you do isolate your leak, I'd love to know the cause. My approach for finding the dval leaks was to take memory dumps and sift through them with MAT, and looking at gc roots there. It was, uhm, fun. If you do get a concise reproducible case, I'd be happy to take a look. |
http://www.everfall.com/paste/id.php?4futm8xwuqtp
Causing memory leaks.
http://www.everfall.com/paste/id.php?7pu6c7acr59i
Don't cause, but uncommenting that line causes memory leak again.
Possibly relevant: http://immutant.org/news/2012/05/18/runtime-isolation/
The text was updated successfully, but these errors were encountered: