Bug #2370: Forked process generates spurious signal errors

• Status: Closed
• Assignee: -
• Target version: 2.0.0
• ruby -v: ruby 1.9.2dev (2009-11-10 trunk 25704) [x86_64-linux]

[orem (Chris Schlaeger)]

=begin
The attached test program demonstrates the problem. About 25% percent of the time the forked-off program terminates with a signal error.

For best results the first parameter of the doRun() call should be set to a value slightly higher than the number of CPU cores in the system.

time ruby19 ruby-signal-bug.rb
Ok: 1513 Errors: 487

real 1m21.352s
user 1m3.712s
sys 0m20.913s

The terminated processes are killed during the IO operation and leave test*.txt files of varying size in the current directory.
The program works fine with ruby 1.8.7 PL27.
=end

[mame (Yusuke Endoh)]

• Status changed from Open to Closed
• % Done changed from 0 to 100

=begin
This issue was solved with changeset r25771.
Chris, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

=end