Memory-leak using "Debug"-option

[bmenne-dspace]

Dear IronPython Support Team

We are using IronPython to call Python from inside a .NET-Application. In our use case we have to debug the Python-Skript. So we enable the "Debug"-option of the ScriptEngine. We found out that the used memory rises by every call.

Please have a look.
Thanks a lot and kind regards

Benedikt

IronPythonDebugLeak.zip

[simplicbe]

Thank you, we will investigate this!

[simplicbe]

I can't see which IronPython version you are using, because with 2.7.6 jdhardy had solved some huge memory leaks.

[bmenne-dspace]

Hi,

Thanks for your quick reply! :)

We use version 2.7.6. If we do not use the "Debug" option everything is fine. Only if the "Debug" option is activated during script execution the memory memory rises by every call.

[jdhardy]

Debug mode keeps a bunch of stuff around that it probably doesn't need to.
When I fixed the memory leaks I deliberately left out Debug mode fixes
because of how it works (it would have required some pretty extensive
changes). It's probably resolvable, but it'll mean spending a lot of time
in dotMemory figuring out what is being held.

Generally, any static variable should be viewed with suspicion, especially
those holding any IronPython object that might hold a PythonContext.

On Wed, Sep 14, 2016 at 12:58 AM, bmenne-dspace [email protected]
wrote:

Hi,

Thanks for your quick reply! :)

We use version 2.7.6. If we do not use the "Debug" option everything is
fine. Only if the "Debug" option is activated during script execution the
memory memory rises by every call.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1411 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGmdR4RIkgMFWecwOpSVLwVIfS4otvKks5qp6kPgaJpZM4J8eZT
.