Message 358187 - Python tracker

➜

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.

Author	jd
Recipients	BreamoreBoy, ajaksu2, jd, jpe
Date	2019-12-10.13:37:06
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1575985026.94.0.481669321044.issue1021318@roundup.psfhosted.org>
In-reply-to

Content
This is actually true and it's quite easy to produce a bug that triggers a segmentation fault when iterating over a large list of threads create dynamically. That makes PyThreadState_Next barely usable for any program that has a few threads. The head mutex needs to be locked to be able to iterate safely over the list of thread.

This is actually true and it's quite easy to produce a bug that triggers a segmentation fault when iterating over a large list of threads create dynamically.

That makes PyThreadState_Next barely usable for any program that has a few threads. The head mutex needs to be locked to be able to iterate safely over the list of thread.

History
Date	User	Action	Args
2019-12-10 13:37:07	jd	set	recipients: + jd, jpe, ajaksu2, BreamoreBoy
2019-12-10 13:37:06	jd	set	messageid: <1575985026.94.0.481669321044.issue1021318@roundup.psfhosted.org>
2019-12-10 13:37:06	jd	link	issue1021318 messages
2019-12-10 13:37:06	jd	create