General

Profile

anmarchenko_datadog (Andrey Marchenko)

  • Login: anmarchenko_datadog
  • Registered on: 03/18/2026
  • Last sign in: 03/18/2026

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 0 1 1

Activity

03/20/2026

04:21 PM Ruby Bug #21959 (Closed): rb_internal_thread_event_hooks_rw_lock is not reinitialized after fork causing deadlocks
Applied in changeset commit:git|c8155822c460a5734d700cd468d306ca03b44ce4.
----------
reinit rb_internal_thread_event_hooks_rw_lock at fork
[Bug #21959]
anmarchenko_datadog (Andrey Marchenko)
10:17 AM Ruby Bug #21959: rb_internal_thread_event_hooks_rw_lock is not reinitialized after fork causing deadlocks
The PR is open: https://github.com/ruby/ruby/pull/16474 anmarchenko_datadog (Andrey Marchenko)
09:44 AM Ruby Bug #21959: rb_internal_thread_event_hooks_rw_lock is not reinitialized after fork causing deadlocks
I am planning to open a PR with proposed fix soon anmarchenko_datadog (Andrey Marchenko)
09:29 AM Ruby Bug #21959 (Closed): rb_internal_thread_event_hooks_rw_lock is not reinitialized after fork causing deadlocks
Ruby's GVL Instrumentation API uses a read-write lock (rb_internal_thread_event_hooks_rw_lock) to protect the list of thread event hooks:
- Read lock — acquired on every GVL transition to iterate and call hook callbacks (rb_thread_execu...
anmarchenko_datadog (Andrey Marchenko)
04:21 PM Ruby Revision c8155822 (git): reinit rb_internal_thread_event_hooks_rw_lock at fork
[Bug #21959] anmarchenko_datadog (Andrey Marchenko)

Also available in: Atom