You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Task which issues a condition.notify(1) to wake up a Task from a set of waiting tasks to perform some task, e.g. consume a piece of data, may hit a race condition with a simultaneous cancel() of a task among the waiting tasks, resulting in none of the tasks
successfully returning from cond.wait(). This is problematic because because the notify() is essentially lost, and starvation/deadlocks may occur.
PR #112201 contains a fix, as well as documentation updates
Bug report
Bug description:
A Task which issues a
condition.notify(1)
to wake up aTask
from a set of waiting tasks to perform some task, e.g. consume a piece of data, may hit a race condition with a simultaneouscancel()
of a task among the waiting tasks, resulting in none of the taskssuccessfully returning from
cond.wait()
. This is problematic because because thenotify()
is essentially lost, and starvation/deadlocks may occur.PR #112201 contains a fix, as well as documentation updates
CPython versions tested on:
CPython main branch
Operating systems tested on:
Windows
Linked PRs
The text was updated successfully, but these errors were encountered: