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 vstinner
Recipients gvanrossum, python-dev, sbt, steve.dower, tim.golden, vstinner, yselivanov, zach.ware
Date 2015-01-23.01:36:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1421976988.77.0.597056601217.issue23095@psf.upfronthosting.co.za>
In-reply-to
Content
Running "runtests.py test_cancel_post_init test_shell" and "runtests.py test_wait_for_handle test_wait_for_handle_cancel" of Tulip show a different behaviour of _WaitHandleFuture. In one case, the cancelled wait is still signaled, on other case, it's never signaled.

Currently, a cancelled _WaitHandleFuture always unregisters the overlapped operation, which causes unexpected event or may lead tests to hang. Never unregisters causes a different issue. Unregistering the overlapped indirectly delete it in memory, which is bad if the completion is still signaled.

A workaround is to keep a reference to the unregistered overlopped, but it's an ugly workaround.
History
Date User Action Args
2015-01-23 01:36:28vstinnersetrecipients: + vstinner, gvanrossum, tim.golden, python-dev, sbt, zach.ware, yselivanov, steve.dower
2015-01-23 01:36:28vstinnersetmessageid: <1421976988.77.0.597056601217.issue23095@psf.upfronthosting.co.za>
2015-01-23 01:36:28vstinnerlinkissue23095 messages
2015-01-23 01:36:27vstinnercreate