-
Notifications
You must be signed in to change notification settings - Fork 440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Data race in tracer/payload.go #2631
Comments
@jared-mackey Thanks for reaching out! We are going to review it. |
We are also experiencing some data races regarding this is similar to the one mentioned above (but read/write are switched)
and this is one data race regarding the reset of the payload:
|
@jared-mackey @SvenGasterstaedt Are you still observing this kind of issue in your services? We tried a few times since April to debug this but no luck yet. Did you reproduce it in higher versions? Thanks! |
@jared-mackey @SvenGasterstaedt If you are still experiencing this issue, we recommend to open a support ticket so we can gather more information. |
Version of dd-trace-go
v1.61.0
Describe what happened:
It appears that there is a data race in reporting traces to DD. Might be related to #330. However, we are seeing it in our staging environment where we have data race detection enabled and sending traces to real DD servers.
Apologies for the poor formatting. Got it from a CSV export from DD logs.
Some other logs that are relevant
Describe what you expected:
No data races :)
Additional environment details (Version of Go, Operating System, etc.):
Golang 1.22.1
Binaries compiled with
-race
Running inside EKS on x86 instances
Agent (“DD servers”) running as a daemonset. Should be a local pod to this pod.
The text was updated successfully, but these errors were encountered: