From: Eric Wong <normalperson@...>
Date: 2018-01-09T07:19:54+00:00
Subject: [ruby-core:84756] Re: [ruby-cvs:68887] mame:r61706 (trunk): Explicit failure in VM_CHECK_MODE when failing to create timer thread

mame@ruby-lang.org wrote:
>   https://svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=revision&revision=61706
> 
>   Log:
>     Explicit failure in VM_CHECK_MODE when failing to create timer thread
>     
>     "warning: pthread_create failed for timer: Resource temporarily
>     unavailable, scheduling broken" still occurs randomly.  This change will
>     allow us to debug the issue.

But you put the assertion for pthread_attr_init failure in your
commit, was that intentional?  I don't think EAGAIN on
pthread_create is avoidable if the system is overloaded.

Maybe pthread_attr_setstacksize fails on some systems, do you
have any info on the system?  Is it Linux?

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>