Right; this article is almost a week old at this point and some progress has been made in addressing this. In particular, I found the characterization that other app servers are not taking action on this problem to be a lie in poor taste.

This kind of talking up of one's own product and saying "we're first; we're best!" rather than working within the ecosystem to help fix a shared issue confirms my feeling that Passenger is a bit of an outlier in the Ruby community.

It's been addressed, but it's a hack. To be safe, apps must stop all other threads before forking.

The only correct fix I can see is to have pre- and post- fork hooks in every library, which make that guarantee.