Segmentation Fault in dd-trace-py on Python 3.12 about dd-trace-py

[sanchda]

👋 Thank you for the report! Unfortunately, this is a known problem in the "stack v2" implementation of the profiler on Python 3.12 (it does not occur in 3.11 or earlier). If you haven't tried the "legacy" stack collector (just omit the DD_PROFILING_STACK_V2_ENABLED environment variable, or use DD_PROFILING_STACK_V2_ENABLED=false), then please give it a shot and see if it offers you some relief.

If you're using "stack v2" for a reason (such as, avoiding the even greater number of segfaults originating from the cpython runtime for the legacy stack collector), then please ignore that advice. 😄

This may actually have been fixed in ddtrace 3.8.4. I'll be testing and working on a fix this upcoming week. I'll check back in on Math 15th or so to confirm whether that version actually has the fix. If you'd like to try the new release to see if it helps, please let me know how that goes!

[sampritipanda]

Thanks, I indeed had DD_PROFILING_STACK_V2_ENABLED and DD_PROFILING_EXPORT_LIBDD_ENABLED enabled to mitigate segfaults from Python 3.11. Should I disable both of them or just STACK_V2?

[sanchda]

👋 sorry, I'm not sure why I lost track of this thread.

If you're using stack v2 in order to mitigate segfaults, then unfortunately there's not much relief. Working on a fix.