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
However, there are multiple sites, which miss checking such conditions. The deadlock could happen when the signal reaches in advance so that the waiting site could lead to a wait forever with no signal notifying anymore.
Hi, developers, it seems there are multiple sites using wait conditions in the wrong ways, which could lead to deadlocks.
Normally, the wait is checked via a condition to ensure the notify that hasn't been executed. For example,
julius/msvc/Library_PortAudio/src/src/hostapi/jack/pa_jack.c
Lines 1025 to 1032 in 4182bf0
julius/msvc/Library_PortAudio/src/src/hostapi/jack/pa_jack.c
Lines 670 to 673 in 4182bf0
However, there are multiple sites, which miss checking such conditions. The deadlock could happen when the signal reaches in advance so that the waiting site could lead to a wait forever with no signal notifying anymore.
julius/msvc/Library_PortAudio/src/src/hostapi/jack/pa_jack.c
Lines 1625 to 1641 in 4182bf0
julius/msvc/Library_PortAudio/src/src/hostapi/jack/pa_jack.c
Lines 1660 to 1668 in 4182bf0
julius/libsent/src/adin/pa/hostapi/jack/pa_jack.c
Lines 1621 to 1637 in 4182bf0
julius/libsent/src/adin/pa/hostapi/jack/pa_jack.c
Lines 1656 to 1664 in 4182bf0
The text was updated successfully, but these errors were encountered: