[Ironpython-users] Analyzing the Memory Leak

[Markus Schaber]

Hi, Jeff,

Von: Jeff Hardy [mailto:jdhardy at gmail.com]
> On Thu, Oct 25, 2012 at 2:27 AM, Markus Schaber <m.schaber at 3s-software.com>
> 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 it works I'll send
> you the licence information.

At least, it's not crashing. However, it traces some of the leaked objects to 
a "Garbage Collector Handle", and it seems it does not record where this
handle was allocated.

However, I now know where the object itself was allocated, and try to step 
through the code to find out where that handle is created.


Best regards

Markus Schaber
-- 
___________________________
We software Automation.

3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50

Email: m.schaber at 3s-software.com | Web: http://www.3s-software.com 
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects

Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915