GeezerVison is showing github.com — bpo-36356: Fix memory leak in _asynciomodule.c during "setup.py build_ext" by btharper · Pull Request #16598 · python/cpython
Conversation
btharper
commented
Oct 5, 2019
•
edited by bedevere-bot
Loading
Uh oh!
There was an error while loading. Please reload this page.
The module seems to be imported twice during the build process which causes a leak. Since these objects are intended to be global for the life of the import, retain them during the second import.
The double import seems to be an artifact of the build system, and not indicative of normal use.
Multiple PRs for BPO-36356 were largely grouped under a single NEWS entry, should this continue to be skipped, or should a new note be added for the 3.9 branch?
https://bugs.python.org/issue36356
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
I think you should add a static _asyncio_module_inited and check that once, as there are many other places that could be initialized twice. I also wonder how exactly can it be imported twice...
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Turns out I was incorrect about the double import. It's importing itself as part of the import process, once as "_asyncio" that then imports itself as "asyncio" gdb trace (with edited paths) below. The spec is passed in from setup.py line 529, but the _module naming convention doesn't seem out of place compared to others (_sha*, _ctypes, _decimal, etc).
#0 module_init () at cpython/Modules/_asynciomodule.c:3251
#1 0x00007ffff2dca8a7 in PyInit__asyncio () at cpython/Modules/_asynciomodule.c:3352
#2 0x000055555593e5ff in _PyImport_LoadDynamicModuleWithSpec (
spec=spec@entry=<ModuleSpec(name='_asyncio', loader=<ExtensionFileLoader(name='_asyncio', path='cpython/build/lib.linux-x86_64-3.9-pydebug/_asyncio.cpython-39d-x86_64-linux-gnu.so') at remote 0x607000ea0320>, origin='cpython/build/lib.linux-x86_64-3.9-pydebug/_asyncio.cpython-39d-x86_64-linux-gnu.so', loader_state=None, submodule_search_locations=None, _set_fileattr=True, _cached=None) at remote 0x607000ea0390>, fp=fp@entry=0x0) at ./Python/importdl.c:164
[... trimmed for brevity ...]
#214 0x000055555593d20c in PyImport_ImportModule (name=name@entry=0x7ffff2dcbe80 "asyncio") at Python/import.c:1482
#215 0x00007ffff2dc3c6f in module_init () at cpython/Modules/_asynciomodule.c:3246
#216 0x00007ffff2dca8a7 in PyInit__asyncio () at cpython/Modules/_asynciomodule.c:3352
#217 0x000055555593e5ff in _PyImport_LoadDynamicModuleWithSpec (
spec=spec@entry=<ModuleSpec(name='_asyncio', loader=<ExtensionFileLoader(name='_asyncio', path='build/lib.linux-x86_64-3.9-pydebug/_asyncio.cpython-39d-x86_64-linux-gnu.so') at remote 0x607000cfc9b0>, origin='build/lib.linux-x86_64-3.9-pydebug/_asyncio.cpython-39d-x86_64-linux-gnu.so', loader_state=None, submodule_search_locations=None, _set_fileattr=True, _cached=None) at remote 0x607000cfca20>, fp=fp@entry=0x0) at ./Python/importdl.c:164
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Updated with a static variable to check initialization. left initialization for the inner call and return early for the outside call, although I don't think the difference would be significant.
If everything looks good I can squash the previous commit since the first one is entirely reverted by the second.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
|
LGTM, but please fix the nit I highlighted.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Good catch, I've fixed the one introduced by this changeset, but grep shows 6 more instances. Would it be worth fixing them along with these changes, or leaving it as it is?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Good catch, I've fixed the one introduced by this changeset, but grep shows 6 more instances. Would it be worth fixing them along with these changes, or leaving it as it is?
@btharper: Which instances? In which file?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
btharper
commented
Oct 7, 2019
•
edited by bedevere-bot
Loading
Uh oh!
There was an error while loading. Please reload this page.
Good catch, I've fixed the one introduced by this changeset, but grep shows 6 more instances. Would it be worth fixing them along with these changes, or leaving it as it is?
@btharper: Which instances? In which file?
Sorry for the lack of specificity. 6 more instances of the closing bracket being on the same line as an else/else if in the Modules/_asynciomodule.c file. I wasn't sure if it would be useful to clean up the rest of the file or just correct what was modified in this PR, though I expect not changing unrelated lines is the safest answer. Anything else for bpo-36356 would be under another PR.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
1st1
commented
Oct 7, 2019
•
edited by bedevere-bot
Loading
Uh oh!
There was an error while loading. Please reload this page.
Sorry for the lack of specificity. 6 more instances of the closing bracket being on the same line as an else/else if in the Modules/_asynciomodule.c file. I wasn't sure if it would be useful to clean up the rest of the file or just correct what was modified in this PR, though I expect not changing unrelated lines is the safest answer. Anything else for bpo-36356 would be under another PR.
We can fix them in a separate PR.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Could you please generate a NEWS entry with blurb?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
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.
LGTM.
I'm fine with merging it with new NEWS entry. It's uncommon to load a C extension twice.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Thanks @btharper for the PR, and @1st1 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8.
🐍🍒⛏🤖
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
I'm fine with merging it with new NEWS entry. It's uncommon to load a C extension twice.
Alright!
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|