Hi, Dino,
Thanks for your vast amount of information.
Von: Dino Viehland [mailto:[email protected]]
> 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
Hi, Dino,
Von: Markus Schaber
> Von: Dino Viehland [mailto:[email protected]]
>> 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,
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 ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New issue] Misleading error message with clr.AddReferenceToFileAndPath on a
UNC path
--
ISSUES
1. [New issue] Misleading error message with
settrace() debugging should be perfectly fine, it's only the .NET debugging
which causes the memory leaks. Can you open a bug and attach the repro? The
repro's simple enough, I might be able to track down the leak fairly quickly.
-Original Message-
From: ironpython-users-bounces+dinov=m
