Segmentation fault when thread is killed during `require`.
One of a library used by us executes
uri-open in multiple thread in parallel under a timeout.
net/http. When the import machinery is killed during performing an import this will lead to a segfault further down the line.
I readily accept that it is very poor practice to do
require in a loop which is suspect to uncatchable exceptions,
But unfortunately the user has no idea that
requires are performed.
The test.rb script from the attachements triggers this bug. You may want to spawn less threads. The high number was chosen to improve the rate of triggering the bug.
We tested this on ruby 2.1.5p273 as shipped with debian Jessie. And ruby 2.2.3p173 from ArchLinux.