Message 329909 - 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	arcivanov
Recipients	arcivanov, augustogoulart, pitrou, taleinat, vstinner
Date	2018-11-14.14:08:05
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1542204485.15.0.788709270274.issue33196@psf.upfronthosting.co.za>
In-reply-to

Content
@vstinner > I'm not sure that I understand the bug. The bug is, if a user makes an error and passes a Queue from context 'fork' to a child that is spawned using 'spawn', the passed Queue is, for obvious reasons, broken. The 'print("Child r_q: %r, %r, %r" % (r_q._rlock, r_q._wlock, r_q._sem), flush=True)' is simply a demonstration of a broken state of the SemLock observed in the child. The expected fix would be to stop the mixed context use of MP objects on the API level (ValueError?) or at least prevent a segfault.

@vstinner

> I'm not sure that I understand the bug.

The bug is, if a user makes an error and passes a Queue from context 'fork' to a child that is spawned using 'spawn', the passed Queue is, for obvious reasons, broken. 

The 'print("Child r_q: %r, %r, %r" % (r_q._rlock, r_q._wlock, r_q._sem), flush=True)' is simply a demonstration of a broken state of the SemLock observed in the child. 

The expected fix would be to stop the mixed context use of MP objects on the API level (ValueError?) or at least prevent a segfault.

History
Date	User	Action	Args
2018-11-14 14:08:05	arcivanov	set	recipients: + arcivanov, pitrou, vstinner, taleinat, augustogoulart
2018-11-14 14:08:05	arcivanov	set	messageid: <1542204485.15.0.788709270274.issue33196@psf.upfronthosting.co.za>
2018-11-14 14:08:05	arcivanov	link	issue33196 messages
2018-11-14 14:08:05	arcivanov	create