-
Notifications
You must be signed in to change notification settings - Fork 747
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@dmitriyse, thanks! @vmuriart, @tonyroberts, @cgohlke, @tiran and @hsoft, please review this. |
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
to
f205d56
Compare
f205d56
to
e9e9051
Compare
ff7e5a1
to
a10b6cc
Compare
a10b6cc
to
507edc9
Compare
CHANGELOG.md
Outdated
@@ -21,6 +21,8 @@ This document follows the conventions laid out in [Keep a CHANGELOG][]. | |||
|
|||
### 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
@dmitriyse can you please resolve a conflict in this PR? |
Yes, I will try to do it on this week. |
0345af2
to
257dcc6
Compare
@denfromufa Could you review this again? |
2145bf2
to
44d606b
Compare
…oduces bugs when CPython freeing up enough objects.
44d606b
to
dbd5fdd
Compare
@filmor i don't see any obvious issues. |
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.
AUTHORS
CHANGELOG