You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all fiber threads end up with a name something like "Ruby-Fiber-15" because we pool those thread objects and reuse them. However, this does not provide very good information about where or why the fiber thread was enlisted.
We could setName on those threads to update the name to something that reflects the origins of the fiber or enumerator using the given fiber thread, which would make it easier to debug when there's a leak or some other issue with those coroutine threads.
The text was updated successfully, but these errors were encountered:
headius
added a commit
to headius/jruby
that referenced
this issue
Apr 6, 2019
This patch sets the name of the threads used to drive fibers (or
the similar Enumerator#next coroutines) in order to more easily
audit and debug those threads. Relates to jruby#5671 and fixesjruby#5670.
Currently all fiber threads end up with a name something like "Ruby-Fiber-15" because we pool those thread objects and reuse them. However, this does not provide very good information about where or why the fiber thread was enlisted.
We could setName on those threads to update the name to something that reflects the origins of the fiber or enumerator using the given fiber thread, which would make it easier to debug when there's a leak or some other issue with those coroutine threads.
The text was updated successfully, but these errors were encountered: