From: Eric Wong <normalperson@...>
Date: 2017-08-23T00:04:24+00:00
Subject: [ruby-core:82452] Re: [Ruby trunk Bug#13794] Infinite loop of sched_yield

charlie@atech.media wrote:
> File sched_yield_1.patch added

> The patch above does not work because
> native_reset_timer_thread runs after fork in the parent.
> Attached an alternative patch that runs in gvl_atfork and
> appears not to run in the parent. Again I do not believe this
> is necessarily the correct way to fix this but I am also
> looking for something that works for me i the meantime.

Agreed that it may not necessarily be an optimal way to fix the
problem; but have you been able to reproduce the problem with
your patch applied?

> Comments appreciated.

Sorry, I've been too distracted this summer.  Will attempt to
concentrate on it, now.

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