[IronPython] Thread local storage in IronPython 2.6

[Michael Foord]

Hello all,

We're working on the port of Resolver One to IronPython 2.6. We're 
finding that in quite a few of our tests our documents are now not being 
garbage collected, which would be a major memory leak in Resolver One if 
left unaddressed.

As far as we can *tell* what is keeping the documents alive is a 
PythonFunctionStack (?) in thread local storage, put there by IronPython 
itself. This doesn't happen with IronPython 2. Does this ring a bell as 
a change in IronPython 2.6?

We're working on this now, so more details if we work it out.

All the best,

Michael Foord

-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog