[IronPython] Thread local storage in IronPython 2.6

[Michael Foord]

Dino Viehland wrote:
>> Yes. Recalculations can be interrupted which uses Thread.Abort (the
>> interrupt can happen during arbitrary user code so it is essentially
>> asynchronous).
>>     
>
> Ok, that could be the source of the leaks.  At least it's the only
> thing that pops out at me while reviewing the code.  I'm not sure that
> we'll actually harden the code against thread abort for 2.6.0 (this is
> really tricky to do) but I can certainly make it so that it won't leak 
> when it actually happens and open a bug to harden it later.
>   

Cool. If it becomes a problem then we'll get in touch and see how we can 
mitigate against it.

At the top level you could put all the cleanup code inside a finally 
block so that thread aborts can't interrupt it. :-)

Michael
>
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>   


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