Salikh Zakirov wrote: > the current implementation of apr_thread_cond_signal() on Windows > has a deficiency: it may lose several concurrent or sequential > signal() calls if more than one thread is waiting on a condition > variable, because there is no count of the number of signal() calls, > and only one woken up thread will really come out of the loop. > ...
I've submitted APR bug 41243 to track this issue.
