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]: ParseCTraceContext may be not memory-safe #32742
Labels
kind/bug
Issues or changes related a bug
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
Comments
longjiquan
added
kind/bug
Issues or changes related a bug
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Apr 30, 2024
/unassign @yanliang567 |
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
Apr 30, 2024
See also milvus-io#32742 Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
May 6, 2024
See also milvus-io#32742 Signed-off-by: Congqi Xia <[email protected]>
congqixia
added a commit
to congqixia/milvus
that referenced
this issue
May 6, 2024
See also milvus-io#32742 Signed-off-by: Congqi Xia <[email protected]>
sre-ci-robot
pushed a commit
that referenced
this issue
May 7, 2024
See also #32742 --------- Signed-off-by: Congqi Xia <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Issues or changes related a bug
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
Is there an existing issue for this?
Environment
Current Behavior
milvus/internal/querynodev2/segments/trace.go
Lines 34 to 44 in 5bb672d
Expected Behavior
spanID and traceID are local variables inner
ParseCTraceContext
, they may be garbage collected after return their address, so it's not safe to use them in cgo code.Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: