ruby.git/thread.c, branch v3_4_9 The Ruby Programming Language [3.4] Fix deadlock on th->interrupt_lock after fork 2026-03-07T04:41:44+00:00 Jean Boussier jean.boussier@gmail.com 2026-02-04T12:12:42+00:00 43771bb0efcd139acd9112a770e8b8d719118dce [Bug #21860] If a thread was holding this lock before fork, it will not exist in the child process. We should re-initialize these locks as we do with the VM locks when forking. Co-Authored-By: John Hawthorn <john@hawthorn.email> Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org> 
[Bug #21860]

If a thread was holding this lock before fork, it will not exist in the
child process. We should re-initialize these locks as we do with the VM
locks when forking.

Co-Authored-By: John Hawthorn <john@hawthorn.email>
Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>
Reapply "merge revision(s) 62430c19c9f1ab49429cebe65f30588472648c95: [Backport #21342]" 2025-09-29T22:10:58+00:00 Takashi Kokubun takashikkbn@gmail.com 2025-09-29T22:10:37+00:00 264b2d78c366491834c9ce4499a4ad7b7564b89d This reverts commit c414b9871f263331cde0af1c08cf5c1a47e1aedf. 
This reverts commit c414b9871f263331cde0af1c08cf5c1a47e1aedf.
Revert "merge revision(s) 62430c19c9f1ab49429cebe65f30588472648c95: [Backport #21342]" 2025-09-29T22:08:47+00:00 Takashi Kokubun takashikkbn@gmail.com 2025-09-29T22:08:47+00:00 c414b9871f263331cde0af1c08cf5c1a47e1aedf This reverts commit 4306c9048fb674d24b92dc46b6746a4749564147. 
This reverts commit 4306c9048fb674d24b92dc46b6746a4749564147.
merge revision(s) 62430c19c9f1ab49429cebe65f30588472648c95: [Backport #21342] 2025-09-29T21:35:15+00:00 Takashi Kokubun takashikkbn@gmail.com 2025-09-29T21:35:15+00:00 4306c9048fb674d24b92dc46b6746a4749564147 Properly unlock locked mutexes on thread cleanup. Mutexes were being improperly unlocked on thread cleanup. This bug was introduced in 050a8954395. We must keep a reference from the mutex to the thread, because if the fiber is collected before the mutex is, then we cannot unlink it from the thread in `mutex_free`. If it's not unlinked from the the thread when it's freed, it causes bugs in `rb_thread_unlock_all_locking_mutexes`. We now mark the fiber when a mutex is locked, and the thread is marked as well. However, a fiber can still be freed in the same GC cycle as the mutex, so the reference to the thread is still needed. The reason we need to mark the fiber is that `mutex_owned_p()` has an ABA issue where if the fiber is collected while it's locked, a new fiber could be allocated at the same memory address and we could get false positives. Fixes [Bug #21342] Co-authored-by: John Hawthorn <john@hawthorn.email> 
	Properly unlock locked mutexes on thread cleanup.

	Mutexes were being improperly unlocked on thread cleanup. This bug was
	introduced in 050a8954395.

	We must keep a reference from the mutex to the thread, because if the fiber
	is collected before the mutex is, then we cannot unlink it from the thread in
	`mutex_free`. If it's not unlinked from the the thread when it's freed, it
	causes bugs in `rb_thread_unlock_all_locking_mutexes`.

	We now mark the fiber when a mutex is locked, and the thread is marked
	as well. However, a fiber can still be freed in the same GC cycle as the
	mutex, so the reference to the thread is still needed.

	The reason we need to mark the fiber is that `mutex_owned_p()` has an ABA
	issue where if the fiber is collected while it's locked, a new fiber could be
	allocated at the same memory address and we could get false positives.

	Fixes [Bug #21342]

	Co-authored-by: John Hawthorn <john@hawthorn.email>
merge revision(s) 0d6263bd416338a339651fb97fe4d62701704c4b: [Backport #21220] 2025-04-14T07:25:55+00:00 Takashi Kokubun takashikkbn@gmail.com 2025-04-14T07:25:55+00:00 1b6f9cd6ea5715ad33d8ba4c78382aa8aafdbcd4 Fix coverage measurement for negative line numbers Fixes [Bug #21220] Co-Authored-By: Mike Bourgeous <mike@mikebourgeous.com> Co-Authored-By: Jean Boussier <jean.boussier@gmail.com> 
	Fix coverage measurement for negative line numbers

	Fixes [Bug #21220]

	Co-Authored-By: Mike Bourgeous <mike@mikebourgeous.com>
	Co-Authored-By: Jean Boussier <jean.boussier@gmail.com>
Check RUBY_THREAD_TIMESLICE value 2024-12-18T02:12:34+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2024-12-13T02:52:19+00:00 57f6329ba7aa744101efe026bea0a0bd46c77fc8 






Add an environment variable for controlling the default Thread quantum
2024-12-13T00:04:49+00:00

Aaron Patterson
tenderlove@ruby-lang.org

2024-11-01T22:06:35+00:00

fffef9aa5d89b6cca3dc634f5278b1fc67fb3d08

This commit adds an environment variable `RUBY_THREAD_TIMESLICE` for
specifying the default thread quantum in milliseconds.  You can adjust
this variable to tune throughput, which is especially useful on
multithreaded systems that are mixing CPU bound work and IO bound work.

The default quantum remains 100ms.

[Feature #20861]

Co-Authored-By: John Hawthorn <john@hawthorn.email>





This commit adds an environment variable `RUBY_THREAD_TIMESLICE` for
specifying the default thread quantum in milliseconds.  You can adjust
this variable to tune throughput, which is especially useful on
multithreaded systems that are mixing CPU bound work and IO bound work.

The default quantum remains 100ms.

[Feature #20861]

Co-Authored-By: John Hawthorn <john@hawthorn.email>







Introduce `Fiber::Scheduler#blocking_operation_wait`. (#12016)
2024-11-20T06:40:17+00:00

Samuel Williams
samuel.williams@oriontransfer.co.nz

2024-11-20T06:40:17+00:00

9c268302bfb4890d3757caa60981802a88bfbd89

Redirect `rb_nogvl` blocking operations to the fiber scheduler if possible
to prevent stalling the event loop.

[Feature #20876]




Redirect `rb_nogvl` blocking operations to the fiber scheduler if possible
to prevent stalling the event loop.

[Feature #20876]






introduce `rb_ec_check_ints()`
2024-11-08T09:02:46+00:00

Koichi Sasada
ko1@atdot.net

2024-11-05T17:31:29+00:00

97aaf6f760259c639dc3ceb3a80fe82411649569

to avoid TLS issue with N:M threads.





to avoid TLS issue with N:M threads.







`interrupt_exec`
2024-11-08T09:02:46+00:00

Koichi Sasada
ko1@atdot.net

2024-11-04T18:55:52+00:00

c8297c3eed571e978dded34dd2036a53d6f28bb3

introduce
- rb_threadptr_interrupt_exec
- rb_ractor_interrupt_exec

to intercept the thread/ractor execution.





introduce
- rb_threadptr_interrupt_exec
- rb_ractor_interrupt_exec

to intercept the thread/ractor execution.