🌐 AI搜索 & 代理 主页
Skip to content

Conversation

@luke-gruber
Copy link
Contributor

Before this change, GC'ing any Ractor object caused you to lose all enabled tracepoints across all ractors (even main). Now tracepoints are ractor-local and this doesn't happen. Internal events are still global.

Fixes [Bug #19112]

@luke-gruber luke-gruber force-pushed the tracepoint_ractor_gc_new branch 6 times, most recently from 8c63624 to 7e80eaf Compare December 10, 2025 17:07
Before this change, GC'ing any Ractor object caused you to lose all
enabled tracepoints across all ractors (even main). Now tracepoints are
ractor-local and this doesn't happen. Internal events are still global.

Fixes [Bug #19112]
Add tracing variables `ruby_vm_iseq_events_enabled` and
`ruby_vm_c_events_enabled`. We can use `ruby_vm_iseq_events_enabled` to
rewrite all traced instructions back to regular instructions, which we
don't do currently. We use `ruby_vm_c_events_enabled` because YJIT
needs this information.
@luke-gruber luke-gruber force-pushed the tracepoint_ractor_gc_new branch from 7e80eaf to 480abc0 Compare December 10, 2025 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant