[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.
stale
indicates no udpates for 30 days
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: