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-120754: Fix memory leak in FileIO.__init__() by vstinner · Pull Request #124225 · python/cpython Conversation
|
|
cc @cmaloney |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
👍 Definitely where the leak is happening / my own tracking finds same location. https://vstinner.github.io/debug-python-refleak.html really helpful in tracking down, thanks for writing up. There's a number of cases where |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Only allocating (PyMem_New) You might include your better fix in a following PR if you want, since you planned more changes for io if I understood correctly. Thanks for reviewing my fix! |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Yep, will make more PRs stat_atopen got several patches moving again.
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Free 'self->stat_atopen' before assigning it, since io.FileIO.__init__() can be called multiple times manually (especially by test_io).
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.