jau::latch: Using condition_variable requires us to hold same mutex lock on modifying count_down() and synchronizing wait*()

Using condition_variable requires us to hold same mutex lock on modifying count_down() and synchronizing wait*().

This is required to not slip the modification of shared variable in count_down()
while synchronizing in wait().

This fixed bug lead to sporadic maximum timouts within latch::wait_for(..),
even though the condition has been reached beforehand, incl. notification.

Notable: The mutex lock shall only be held during modification and
the corresponding condition_variable wait-loop.
The notify*() still shall be issued w/o lock, i.e. out of mutex scope,
to avoid inefficient double-lock at wait*().

0 files changed, 0 insertions, 0 deletions