duerst / it.aoyama.ac.jp wrote:
> File strace_after_ctrl_C.txt added
> 
> > This then also 'hangs', with CPU usage 0.0%. My understanding would be that this means that `strace` doesn't have much to show because there's nothing going on on the Ruby side.
> 
> Attached is the rest of the strace output, after I hit Ctrl-C on the Ruby side. Not sure it will help anything.

Thanks, but lots of stuff in there I don't understand since it's
not Linux...

Did Cygwin use sleepy timer-thread in Ruby 2.5 and earlier?

If not, can you try a 3rd patch to disable sleepy timer-thread?
(thread_win32.c doesn't use sleepy timer thread, either)

This 3rd patch goes on top of the previous two:

  https://80x24.org/spew/20181015223141.18303-1-e / 80x24.org/raw

The 3 patch series should be:

      thread_pthread.c: fall back to UBF_TIMER_PTHREAD for Cygwin
      thread_pthread.c: check and reset interrupts for UBF_TIMER_PTHREAD
      thread_pthread.c: do not use sleepy timer thread on Cygwin

Footnote: Sleepy timer thread is ideal if your platform supports it
because it reduce CPU wakeups and therefore power consumption.

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