Yes, you are correct. The mutex holds. I had my head in java synchronized waits for a second *shudder*...
> Am 23.10.2015 um 12:05 schrieb Yann Ylavic <[email protected]>: > > On Fri, Oct 23, 2015 at 11:59 AM, Stefan Eissing > <[email protected]> wrote: >> >> The problem with the unlock in release is that the h2_mplx might have been >> destroyed by then, as the signal might give the lock to someone waiting. > > Hm, h2_mplx_release_and_join() (which destroys the mplx) won't be > woken up until the mutex is released, since > apr_thread_cond_timedwait() acquires the mutex.
