Message 331201 - Python tracker

Message331201

Author	vstinner
Recipients	pablogsal, vstinner
Date	2018-12-06.01:00:33
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1544058034.55.0.788709270274.issue35424@psf.upfronthosting.co.za>
In-reply-to

Content
Since 2 years, I'm fixing frequently "dangling thread" and "dangling process" warnings on buildbots. These bugs are really hard to reproduce. They usually require to get access to a specific buildbot, simulate a specific workload, and get the proper timing to get the warning. I propose to emit a ResourceWarning in multiprocessing.Pool destructor if the pool has not been cleaned properly. I'm not sure in which cases a warning should be emitted. Attached PR is a WIP implementation.

Content

Since 2 years, I'm fixing frequently "dangling thread" and "dangling process" warnings on buildbots. These bugs are really hard to reproduce. They usually require to get access to a specific buildbot, simulate a specific workload, and get the proper timing to get the warning.

I propose to emit a ResourceWarning in multiprocessing.Pool destructor if the pool has not been cleaned properly. I'm not sure in which cases a warning should be emitted.

Attached PR is a WIP implementation.

History
Date	User	Action	Args
2018-12-06 01:00:35	vstinner	set	recipients: + vstinner, pablogsal
2018-12-06 01:00:34	vstinner	set	messageid: <1544058034.55.0.788709270274.issue35424@psf.upfronthosting.co.za>
2018-12-06 01:00:34	vstinner	link	issue35424 messages
2018-12-06 01:00:33	vstinner	create