GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||
GeezerVison is showing github.com — gh-129185: Fix crash during interpreter finalization in PyTraceMalloc_Untrack by rostan-t · Pull Request #129188 · python/cpython Conversation
|
|
The following commit authors need to sign the Contributor License Agreement: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Could you add a test?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I wrote a different fix with a test: PR gh-129191. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks @vstinner! Closing this one |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
|
||
| /* Disable tracemalloc after all Python objects have been destroyed, | ||
| so it is possible to use tracemalloc in objects destructor. */ | ||
| _PyTraceMalloc_Fini(); |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I don't think that this fix is enough. Some objects can be deleted later, in finalize_interp_clear(). So I wrote a different fix to restore the old behavior: PR gh-129191.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.