Hi, Jeff,
Von: Jeff Hardy [mailto:jdha...@gmail.com]
> On Thu, Oct 25, 2012 at 2:27 AM, Markus Schaber
> wrote:
> > ... Excellent analysis ...
>
> > Do you know of any other good and free (as in beer) tool for memory
> debugging?
>
> JetBrains' dotTrace. It's not free, but the IronPython projec
ellect.com
-Original Message-
From: Ironpython-users
[mailto:ironpython-users-bounces+rome=wintellect@python.org] On Behalf Of
Jeff Hardy
Sent: Thursday, October 25, 2012 10:39 AM
To: Markus Schaber
Cc: Discussion of IronPython
Subject: Re: [Ironpython-users] Analyzing the Memory Leak
On Thu, Oc
On Thu, Oct 25, 2012 at 2:27 AM, Markus Schaber
wrote:
> ... Excellent analysis ...
> Do you know of any other good and free (as in beer) tool for memory debugging?
JetBrains' dotTrace. It's not free, but the IronPython project has an
OSS licence and there's a free trial. Give it a spin and if i
Hi,
I'm currently trying to analyze the memory leak
http://ironpython.codeplex.com/workitem/31764
One thing I found out so far is that sys.settrace (which is called by
Python.SetTrace internally) seems to call pyContext.PushTracebackHandler
without ever pulling that handler.
I did insert som
