[Ironpython-users] IronPython, Daily Digest 9/24/2013

[CodePlex]

Hi ironpython,

Here's your Daily Digest of new issues for project "IronPython".

In today's digest:ISSUES

1. [New comment] Memory Leak

----------------------------------------------

ISSUES

1. [New comment] Memory Leak
http://ironpython.codeplex.com/workitem/31764
User jdhardy has commented on the issue:

"<p>@koreney: That ownership chain is incredibly useful. If this happens routinely it should be possible from a debugger to figure out (a) how many DebugContext instances there are, and (b) what the owners of those DebugContexts are, it might be possible to track down what is keeping stuff alive. It might require windbg to do it, unfortunately. It's quite possible that there are places currently using strong references that should be replaced with weak references to prevent this sort of thing.</p><p>I really dislike the idea of requiring users to take a manual step to avoid a memory leak; it should be something that's handled automatically. I'd prefer to find the root cause and eliminate that, but as a workaround ResetAllSourceFiles() could be called inside the Execute() function or something.</p>"
----------------------------------------------



----------------------------------------------
You are receiving this email because you subscribed to notifications on CodePlex.

To report a bug, request a feature, or add a comment, visit IronPython Issue Tracker. You can unsubscribe or change your issue notification settings on CodePlex.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20130925/92fd1af3/attachment.html>