Re: [Ironpython-users] Analyzing the Memory Leak

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

Re: [Ironpython-users] Analyzing the Memory Leak

To add another recommendation... SciTech's Memory Profiler has a 7-day trial (non-consecutive... so you can use it one day a month for 7 months if you want). SciTech is what many people swear by - having used dotTrace, ANTS, and even good 'ole CLR Profiler and low-level heap walking in WinDBG/S

Re: [Ironpython-users] Analyzing the Memory Leak

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

[Ironpython-users] Analyzing the Memory Leak

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