[ruby-core:24584] Re: [Bug #1525] Deadlock in Ruby 1.9's VM caused by ConditionVariable.wait and fork?

Eric Wong wrote:
> Issue #1525 has been updated by Eric Wong.
>
>
> Looking at trunk, there doesn't seem to be any accounting of mutexes to pass to
> handlers for pthread_atfork; so the child process will just inherit the mutexes
> in an unknown state.
>
>   
Yes.
> It should be possible to fix the problem by keeping track of all mutexes as
> they're created/initialized and registering pthread_atfork handlers
> to ensure all mutexes are unlocked when the child starts running.
>
>   
In fact, it is impossible to track all mutexes because the usage of 
mutexes really
depends on the underlying implementation.
For example, the deadlock on this issues doesn't happen on Linux system, 
even
not on FreeBSD7.2, but happens on FreeBSD6.4.

Thanks
-Tetsu