[IronPython] IronPython is leaking

Martin Maly Martin.Maly at microsoft.com
Wed Dec 21 18:44:02 CET 2005


This is a known problem in IronPython. The code generated using Evaluate is currently not generated as garbage-collectable code. This is a something that we have yet to fix. In the meantime what might help is pre-compiling the code and then execute/eval the code already compiled.

Martin

-----Original Message-----
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Andrew Pliszka
Sent: Wednesday, December 21, 2005 9:13 AM
To: Discussion of IronPython
Subject: [IronPython] IronPython is leaking

Hi,

I run a very simple speed/reliability test using IronPython, and then
analysed the code using .Net Profiler. Current IronPython release seams to
not release all the resources, because the memory usage of simple console
application doubles in size from 62MN to 120MB, and analyzing .Net Profiler
GC graphs there is a linear increase in memory usage.

I run the same test using Boo (http://boo.codehaus.org/) and there was no
problems.

I am interested in using IronPython as a scripting language for my
application. Is there a release date for production ready IronPython?

Andrew

ConsoleProgram.cs
...
            PythonEngine pe = new PythonEngine();
            pe.AddToPath(Environment.CurrentDirectory);
            pe.Execute("import hello");

            for (int j = 0; j < 1; j++)
                for (int i = 0; i < 6000; i++)
                	pe.Evaluate("hello.speedLoop()")
...

hello.py

def speedLoop():
	j = 0;
	i = 0;
	x = 0;
	while i < 10000:
		while x < 10000:
			j = i;
			x = x + 1;
		i = i + 1;
	return i;


-----Original Message-----
From: users-bounces at lists.ironpython.com
[mailto:users-bounces at lists.ironpython.com]On Behalf Of J. Merrill
Sent: Wednesday, December 21, 2005 11:57 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Comparing enum to None


I for one would prefer for you to continue to send reports to the list.
That way, I'll know about the issue, and will see any answer -- particularly
one of the form "it's a bug, but we won't be able to fix it for a while
[because ...], so do this instead" or "we'll fix it soon, but for now here's
a workaround" or "not a bug, because ...".

Thanks.

At 09:01 AM 12/21/2005, William Reade wrote (in part)
>Hi, we have a bug report. [snip]
>Incidentally, should we be bothering the list with these things, or
>should we put them directly into the bug tracker?


J. Merrill / Analytical Software Corp

_______________________________________________
users mailing list
users at lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

_______________________________________________
users mailing list
users at lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com



More information about the Ironpython-users mailing list