So I'm suspicious that that may have something to do with it (mostly just based on the name of that class :) ).
It's possible/likely that the actual ruby code we're running inside of the JRuby ScriptingContainer has memory leaks that we need to fix, but I'd have guessed / hoped that GC'ing the ScriptingContainer would be a feasible workaround for freeing up that memory.
I don't have a tremendous amount of experience debugging JVM -> native memory allocation, so if anyone has any pointers on how to debug this, they'd be greatly appreciated! I'm also happy to take this to a mailing list, IRC, etc. if there is a more appropriate forum.
The text was updated successfully, but these errors were encountered:
@yokolet - Thanks for the response. Unfortunately, your proposed solution doesn't work for our use-case - we are using persistent ScriptingContainers that are initialized on application startup. Our main reason for doing this is that we need to load a relatively large ruby codebase into each container, and this is a time-consuming process. So we never terminate or finalize a ScriptingContainer until the application shuts down.