:* Re: [IronPython] Memory leaks in Ipy 2.6
2.6.1 is when it should be fixed which should be sometime early next year.
A better workaround might be to avoid try/except in the generator if you can
refactor that out into its own function. But if that doesn’t work then I
also think calling close explicitly s
do so without the cost of
throwing the exception.
From: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of Idan Zaltzberg
Sent: Monday, December 28, 2009 11:52 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Memory leaks in Ipy 2.6
Thanks for the fast
python.com [mailto:
users-boun...@lists.ironpython.com] *On Behalf Of *Dino Viehland
*Sent:* Monday, December 28, 2009 9:47 PM
*To:* Discussion of IronPython
*Subject:* Re: [IronPython] Memory leaks in Ipy 2.6
This is definitely a bug – we’re leaking our stack frames on the CLR’s
finalizer thre
boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of Idan Zaltzberg
Sent: Monday, December 28, 2009 10:33 AM
To: users@lists.ironpython.com
Subject: [IronPython] Memory leaks in Ipy 2.6
Hi,
Working with the new version I have encountered some problems which look like
Hi,
Working with the new version I have encountered some problems which look
like memory leaks to me.
I've written 3 test methods that reproduce the problems, and would
appreciate your response.
Thanks
*Problem 1*
Occurs when you do the all of the following
1. Define a generator method
