ROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Szymon Kobalczyk
Sent: Wednesday, December 21, 2005 2:30 PM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython is leaking
Martin Maly wrote:
>This is a known problem in IronPython. The code generated using Evaluate is
>curren
: [IronPython] IronPython is leaking
Martin Maly wrote:
>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 exec
Martin Maly wrote:
>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 c
But, but...
If MN = Meganybble, then 62MN = 31MB. In which case, 31MB -> 120MB is
nearly quadrupled, not doubled!
;)
-
Keith J. Farmer // [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrew Pliszka
Sent: Wednesday, 21 December 2
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
-O
