Repository navigation
Py_Finalize() doesn't stop daemon threads #68958
Description
| BPO | 24770 |
|---|---|
| Nosy | @ericsnowcurrently |
| Superseder |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2019-12-20.23:33:07.623>
created_at = <Date 2015-08-01.06:08:55.461>
labels = ['extension-modules', 'interpreter-core', '3.8', '3.9', 'type-crash']
title = "Py_Finalize() doesn't stop daemon threads"
updated_at = <Date 2019-12-20.23:33:07.617>
user = 'https://bugs.python.org/AlexBudovski'bugs.python.org fields:
activity = <Date 2019-12-20.23:33:07.617>
actor = 'eric.snow'
assignee = 'none'
closed = True
closed_date = <Date 2019-12-20.23:33:07.623>
closer = 'eric.snow'
components = ['Extension Modules', 'Interpreter Core']
creation = <Date 2015-08-01.06:08:55.461>
creator = 'Alex Budovski'
dependencies = []
files = []
hgrepos = []
issue_num = 24770
keywords = []
message_count = 2.0
messages = ['247798', '358746']
nosy_count = 2.0
nosy_names = ['eric.snow', 'Alex Budovski']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = '36476'
type = 'crash'
url = 'https://bugs.python.org/issue24770'
versions = ['Python 3.8', 'Python 3.9']
Activity
AlexBudovski commentedon Aug 1, 2015
This is a known issue, from the comment, but it is causing AVs for my embedded application when background threads are created, for example, by the _socket builtin module.
/* Undo the effect of Py_Initialize().
Beware: if multiple interpreter and/or thread states exist, these
are not wiped out; only the current thread and interpreter state
are deleted. But since everything else is deleted, those other
interpreter and thread states should no longer be used.
(XXX We should do better, e.g. wipe out all interpreters and
threads.)
Locking: as above.
*/
[-]Py_Finalize not cleaning up all threads[/-][+]Py_Finalize() doesn't stop daemon threads[/+]ericsnowcurrently commentedon Dec 20, 2019
I'm closing this in favor of bpo-36476 "Runtime finalization assumes all other threads have exited."