trace: fix span leak in batchSpanProcessor #5518
Open
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.
Description
When a span
ReadOnlySpan
is processed and then exported bybatchSpanProcessor
it may be not garbage collected. A strong pointer to aReadOnlySpan
may be kept inbatchSpanProcessor.batch
slice.Environment
Steps To Reproduce
Expected behavior
There are no references to the
leaked_span
in thebatchSpanProcessor
Actual behavior
There is a references to the
leaked_span
in thebatchSpanProcessor.batch
PR description
In this PR
batchSpanProcessor
clears references to spans after export.