You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 14, 2018. It is now read-only.
Hi,
We are using IronPython every day and we can solve every job with it.
However we would like to use unlimited number of IronPython runtimes in an application now and preload some runtimes on starting to be faster later.
I made a little demo for the bug we have found.
The traceback import is the most important part of the code.
Maybe the traceback module is made for CPython where I cannot image such a scenario but in IronPython it is possible to use multiple runtimes in an application.
The demo can result various misterious crashes.
The goal would be that it could run on a multi core PC.
Sometimes a Thread.Sleep(400) between the thread start methods helps sometimes does not.
Sometimes the bug appears only after a PC restart.
Weakref seems like the common thread (ahem) in this case. There must be a synchronization issue in the weakref code, and I think there might be a couple of other open issues that have a similar problem.
Hi,
We are using IronPython every day and we can solve every job with it.
However we would like to use unlimited number of IronPython runtimes in an application now and preload some runtimes on starting to be faster later.
I made a little demo for the bug we have found.
The traceback import is the most important part of the code.
Maybe the traceback module is made for CPython where I cannot image such a scenario but in IronPython it is possible to use multiple runtimes in an application.
The demo can result various misterious crashes.
The goal would be that it could run on a multi core PC.
Sometimes a Thread.Sleep(400) between the thread start methods helps sometimes does not.
Sometimes the bug appears only after a PC restart.
Best Regards
David Fulop
The text was updated successfully, but these errors were encountered: