[IronPython] Bug fixes in Ipy 2.6.1
dinov at microsoft.com
Thu Feb 18 17:15:59 CET 2010
This is interesting - there's a .NET exception object which is keeping a traceback frame alive which is keeping the just_numbers list alive. We should clear out the local .NET exception and the memory will then be eligible for collection. The good news is that as soon as this method is no longer on the stack the memory is reclaimable (so it's really just that we're not collecting soon enough - not that we're actually leaking the memory) but we should fix it anyway.
I've opened this bug: http://ironpython.codeplex.com/WorkItem/View.aspx?WorkItemId=26244
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Idan Zaltzberg
Sent: Thursday, February 18, 2010 2:58 AM
To: users at lists.ironpython.com
Cc: Ronnie Maor; Avner Rosenan
Subject: [IronPython] Bug fixes in Ipy 2.6.1
In Ipy 2.6 there some issues of memory leak when using generator methods.
I downloaded Ipy 2.6.1 RC1 and indeed most of them were fixed.
Still, one issue still remains the same but I'm not entirely sure this is a real bug:
The following code shows that in some cases, some memory is not released even after GC, is that ok?
just_numbers = range(1,1000000)
raise Exception("some exception") # comment out this line to make the test not work
from System import GC
for _ in xrange(4):
before = get_memory()
crt = coroutine()
crt = None
after = get_memory()
self.assert_(after-before > 10,'There should be a memory leak in this case.before=%s after=%s' % (before,after))
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironpython-users