Charles Oliver Nutter

> TruffleRuby currently does not attempt to kill unreachable Fibers This is not feasible. People walk away from fibers all the time, especially those behind `Enumerator#next`. We have seen code...

The biggest problem, as I see it, is that fibers are frequently used when calling third-party libraries that may have ensure clauses with important side effects. By allowing fibers to...

> CRuby does not execute ensure clauses for Fibers since at least 1.9 and I guess the issue is so old it will never change And yet the issue has...

Also... > (It is possible to run them on process exit, that's a separate concern, there we have a natural point where other Fibers are not executing and there is...

> Anyway, if you prefer to let JRuby users find out that their code using Fibers runs unexpectedly in parallel and causes weird race conditions, it is your decision, I...

Examine shutdown logic for orphaned fibers in 9.3.1. This may relate to #6004 and other unsolved fiber leaks. It may be that we should be more aggressive when killing orphaned...

This naive attempt does not work right and we will need to explore this further as in #7103. I believe this change will be too aggressive to do in 9.3...

@toy Can you tell us how critical this functionality is to your library? The changes needed to support this efficiently are too drastic to do in a 9.3.x release, and...

It is an interesting idea! I am not entirely sure where all the warnings were added, but perhaps the specs are enough? I do have to say this is probably...

No progress on this. It would be a good beginner or help wanted item... find the missing warnings in spec runs, figure out where the warning should happen, and add...