- Notifications
You must be signed in to change notification settings - Fork768
Fixed Second PythonEngine.Initialize call, all sensitive static variables now reseted.#534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
mention-bot commentedAug 31, 2017
@dmitriyse, thanks!@vmuriart,@tonyroberts,@cgohlke,@tiran and@hsoft, please review this. |
codecovbot commentedAug 31, 2017 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov Report
@@ Coverage Diff @@## master #534 +/- ##==========================================+ Coverage 68.55% 77.19% +8.64%========================================== Files 1 63 +62 Lines 283 5754 +5471 Branches 0 907 +907 ==========================================+ Hits 194 4442 +4248- Misses 89 1013 +924- Partials 0 299 +299
Continue to review full report at Codecov.
|
27905c8 tof205d56Comparef205d56 toe9e9051Compareff7e5a1 toa10b6ccComparea10b6cc to507edc9CompareCHANGELOG.md Outdated
| ###Fixed | ||
| - Fixed secondary PythonEngine.Initialize call, all sensitive static variables now reseted. | ||
| This is a hidden bug. Once python cleaning up enough memory, objects from previous engine run becomes corrupted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
please include reference to this PR
den-run-ai commentedJun 24, 2018
@dmitriyse can you please resolve a conflict in this PR? |
dmitriyse commentedJun 25, 2018
Yes, I will try to do it on this week. |
filmor commentedOct 29, 2018
@denfromufa Could you review this again? |
…oduces bugs when CPython freeing up enough objects.
den-run-ai commentedNov 14, 2018
@filmor i don't see any obvious issues. |
Uh oh!
There was an error while loading.Please reload this page.
What does this implement/fix? Explain your changes.
This change fixes hidden bug. Once python cleaning up enough memory, objects from previous engine run becomes corrupted and produces segfault.
...
Does this close any currently open issues?
It's required but not enough to fix this issue
#499
...
Any other comments?
Described problem never pop up, because ~PyObject currently does not called by the GC (due to some reasons). So many many time pythonnet lives without garbage collection with constant memory leak.
...
Checklist
Check all those that are applicable and complete.
AUTHORSCHANGELOG