From: <fwi...@gm...> - 2012-12-12 00:13:33
|
On Tue, Nov 20, 2012 at 8:43 AM, Tim Fox <tim...@gm...> wrote: > Hi there, > > We are currently using Jython as the Python engine in the Vert.x project > > https://github.com/vert-x/vert.x > http://vertx.io/ > > We use Jython embedded and every time we deploy some Python code in Vert.x > it runs in its own instance of PythonInterpreter and its own PySystemState > > Unfortunately after an instance of PythonInterpreter has been gc'd the > PySystemState leaks. > > This is due to the following known issues: > > http://bugs.jython.org/issue1327 (Leak via thread locals) > > http://bugs.jython.org/issue1746 (Leak via static private member > 'searchPaths' in class org.python.core.codecs) > > Is there any chance that fixes to the above will make it into an official > Jython release before long. > > I have hacked the code locally to partially work around the issues using > reflection, but this is _extremely_ hacky, won't work in a restricted > security sandbox, and has performance issues. > > The other possibility is we work fork Jython and fix it ourselves (the fixes > don't appear difficult), but I'd much rather work with an 'official' > release. > > Any help greatly appreciated.. and thanks for a great project! Sorry for the slow response. We do expect to close these leaks for Jython 2.7. I think backwards compatibility issues prevent fixing this in 2.5 - at least that's what Jim Baker (who was the main driver on these changes) told me previously. The "before long" part is harder to say - I hope to get a beta out early in the new year, and I really hope to get a final out before Pycon 2013 in March, but it is foolish to try to give iron clad promises... -Frank |