nov=microsoft@python.org [mailto:
> ironpython-users-bounces+dinov=microsoft@python.org] On Behalf Of
> Markus Schaber
> Sent: Wednesday, November 16, 2011 1:40 AM
> To: Markus Schaber; ironpython-users@python.org
> Subject: Re: [Ironpython-users] Memory Leak and Lightweight S
nces+dinov=microsoft@python.org
[mailto:ironpython-users-bounces+dinov=microsoft@python.org] On Behalf Of
Markus Schaber
Sent: Wednesday, November 16, 2011 1:40 AM
To: Markus Schaber; ironpython-users@python.org
Subject: Re: [Ironpython-users] Memory Leak and Lightweight Scopes
Hi,
Hi,
Von: Markus Schaber
>[Memory Leaks]
I now created a smaller stand-alone testcase simulating our environment, and
isolated the following cases:
- using Python.SetTrace(engine, delegate) leaks about 165k per script
invocation.
- importing the warning module from the hosting environment lea
Hi, Dino,
Von: Markus Schaber
> Von: Dino Viehland [mailto:di...@microsoft.com]
>> Also make sure that you don't have debugging enabled as that forces to
>> create uncollectible code too and probably overrides the light weight scopes
>> option.
> I'll first try to check that one. The reason is
Hi, Dino,
Thanks for your vast amount of information.
Von: Dino Viehland [mailto:di...@microsoft.com]
> Also make sure that you don't have debugging enabled as that forces to create
> uncollectible code too and probably overrides the light weight scopes option.
I'll first try to check that on
Marcus wrote:
> Hi,
>
> We currently have a massive memory leak using IronPython hosted in our
> application (about 10-15 MB per script run).
>
> Googling brought up that using the LightweightScopes option should solve
> that problem. However, I was not able to find any documentation about the
>
Hi,
We currently have a massive memory leak using IronPython hosted in our
application (about 10-15 MB per script run).
Googling brought up that using the LightweightScopes option should solve that
problem. However, I was not able to find any documentation about the
implications of lightweight
