| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@dmitriyse, thanks! @vmuriart, @tonyroberts, @cgohlke, @tiran and @hsoft, please review this. |
Sorry, something went wrong.
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.
|
Sorry, something went wrong.
| ### 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.
please include reference to this PR
Sorry, something went wrong.
|
@dmitriyse can you please resolve a conflict in this PR? |
Sorry, something went wrong.
|
Yes, I will try to do it on this week. |
Sorry, something went wrong.
|
@denfromufa Could you review this again? |
Sorry, something went wrong.
…oduces bugs when CPython freeing up enough objects.
|
@filmor i don't see any obvious issues. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
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.