[PROF-13286] Disable heap profiling on Ruby 4 due to incompatibility#5148
Merged
Conversation
**What does this PR do?** This PR disables the heap profiling feature when running on Ruby 4 as the current implementation (that relies on object_id) is not safe to use on Ruby 4. **Motivation:** Avoid impacting applications running on Ruby 4. **Additional Notes:** Discussion with the Ruby core team in https://bugs.ruby-lang.org/issues/21710 has uncovered that our use of object_id from inside the NEWOBJ tracepoint is not safe on Ruby 4, and it's likely it can't be made safe. Until we're able to replace the Datadog profiler's usage of object_id for heap profiling, we won't be able to safely offer this feature on Ruby 4. (We temporarily disabled the heap profiler for 4.0.0-preview2 in #5091 and re-enabled it in #5121 when it looked fixed but discussion on the upstream ticket uncovered further issues) **How to test the change?** Validate that profiler doesn't enable heap profiling on Ruby 4.
|
Thank you for updating Change log entry section 👏 Visited at: 2025-12-16 00:05:54 UTC |
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage 🔗 Commit SHA: 4076741 | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
ivoanjo
added a commit
to DataDog/documentation
that referenced
this pull request
Dec 15, 2025
…with Ruby 4 **What does this PR do?** This PR pairs with DataDog/dd-trace-rb#5148 on the Ruby profiler side to document that heap profiling is not currently compatible with Ruby 4. **Motivation:** Document this limitation clearly, to avoid confusing customers.
1 task
BenchmarksBenchmark execution time: 2025-12-15 18:08:31 Comparing candidate commit 4076741 in PR branch Found 1 performance improvements and 1 performance regressions! Performance is the same for 42 metrics, 2 unstable metrics. scenario:profiling - hold / resume
scenario:profiling - intern_all 1000 repeated strings
|
p-datadog
approved these changes
Dec 16, 2025
ivoanjo
added a commit
to DataDog/documentation
that referenced
this pull request
Dec 16, 2025
…with Ruby 4 (#33363) **What does this PR do?** This PR pairs with DataDog/dd-trace-rb#5148 on the Ruby profiler side to document that heap profiling is not currently compatible with Ruby 4. **Motivation:** Document this limitation clearly, to avoid confusing customers.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR disables the heap profiling feature when running on Ruby 4 as the current implementation (that relies on object_id) is not safe to use on Ruby 4.
Motivation:
Avoid impacting applications running on Ruby 4.
Change log entry
Yes. Disable heap profiling on Ruby 4 due to incompatibility
Additional Notes:
Discussion with the Ruby core team in https://bugs.ruby-lang.org/issues/21710 has uncovered that our use of object_id from inside the NEWOBJ tracepoint is not safe on Ruby 4, and it's likely it can't be made safe.
Until we're able to replace the Datadog profiler's usage of object_id for heap profiling, we won't be able to safely offer this feature on Ruby 4.
(We temporarily disabled the heap profiler for 4.0.0-preview2 in #5091 and re-enabled it in #5121 when it looked fixed but discussion on the upstream ticket uncovered further issues)
How to test the change?
Validate that profiler doesn't enable heap profiling on Ruby 4.