Fix Jython memory leak #7
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jython eval acts like an interpreter - any intermittently declared variables can be preserved. The PythonInterpreter is also frustratingly persistent and resists clean-up attempts.
This has led to a memory leak in our Jython script language (see http://fiji.sc/bugzilla/show_bug.cgi?id=1203).
To fix this, a PhantomReference is used to monitor when its corresponding JythonScriptEngine is garbage collected, at which point the PythonInterpreter is forcefully cleaned of local variables.
To avoid mutual hard references, the JythonScriptEngine and containing ScriptModule must never be passed to the PythonInterpreter. Instead, they can be cached in a Java-side map to weak references.