Issue 24853: Py_Finalize doesn't clean up PyImport_Inittab (original) (raw)

Issue24853

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/69041

classification

process

Created on 2015-08-13 02:10 by Alex Budovski, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (5)
msg248495 - (view)	Author: Alex Budovski (Alex Budovski)	Date: 2015-08-13 02:10
This means initialize/run script/finalize will crash the second time, since the inittab can have stale entries.
msg272425 - (view)	Author: Simon McVittie (smcv) *	Date: 2016-08-11 08:51
http://bugs.python.org/issue27736 might be related, or even a duplicate of this.
msg272925 - (view)	Author: STINNER Victor (vstinner) *	Date: 2016-08-17 12:06
> This means initialize/run script/finalize will crash the second time, since the inittab can have stale entries. Sorry, I don't understand. inittab: do you mean _PyImport_Inittab defined in Modules/config.c or PC/config.c? This table is constant, no? Are you able to reproduce a crash? I suggest to close the issue as not a bug :-p
msg272947 - (view)	Author: Xiang Zhang (xiang.zhang) *	Date: 2016-08-17 14:18
> initialize/run script/finalize will crash the second time I don't think so since we already get a test case in test_capi that does init/fini repeatedly. It does not crash. So I agree to close this one.
msg272953 - (view)	Author: STINNER Victor (vstinner) *	Date: 2016-08-17 14:26
The issue was fixed by a previous change, maybe the issue #27736.