I don't see how the strace itself indicates a problem on its own. SIGVTALRM is what Ruby uses for signaling/interrupting the "thread of execution" (to context switch between threads, etc),
What does your app do? What are its gem dependencies (more importantly, what are its natively-compiled extension gem dependencies)? Does the patch you incorporated solve your hung-ruby problem reliably?
Reading through the current release-2010.02 codebase, I see there's already a START_TIMER() a few lines above the diff you reference in the ticket. It doesn't make sense offhand how a second call to START_TIMER() would solve a hung-ruby problem (I believe all it would do is just reset the itimer countdown).
On Oct 17, 2010, at 4:17 AM, Gleb Pomykalov wrote:
> The issue is quite critical. There are a lot of dead processess on > production servers. Can you please comment out the problem?
> Thank you
> -- > You received this message because you are subscribed to the Google Groups "Ruby Enterprise Edition" group. > To post to this group, send email to firstname.lastname@example.org. > To unsubscribe from this group, send email to email@example.com. > For more options, visit this group at http://groups.google.com/group/emm-ruby?hl=en.