It can happen that the ThreadedNexter#shutdown from RubyEnumerator sends interrupts to a thread that is executing a different task.

ThreadedNexter#shutdown can get the thread value before the Nexter thread is finished but send the interrupts after the Nexter thread is already done with its work. In case that the Nexter thread is already assigned another task those interrupts can cause problems.

From what I could see it seems it affects all JRuby versions with ThreadedNexter.

To reproduce the issue:

threads = []

200.times do
  threads << Thread.new do
    enumerable1 = (1..1000)
    enumerable2 = (1..1000)
    100.times do
      enumerable1.zip(enumerable2).map { |(a, b)| a^b }
    end
  end
end

threads.each(&:join)

Related to #2577 and #2824