You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CloseGuard::drop from here is the only way to call DataInner::clearhere.
This results in the DataInner not being freed (memory leak I believe), and the parent span not having it's ref_count decremented, leading to the parent span being stuck in limbo for eternity.
I ran into this when wrapping the registry type to have it behind an Arc to do some OTEL shenanigans with more than 32 tracing fields.
The text was updated successfully, but these errors were encountered:
* Adds a function `set_attribute` to `OpenTelemetrySpanExt` to allow
setting attributes directly on the OpenTelemetry `SpanBuilder`.
This allows users to set more than the tracing maximum of 32 fields.
There was a workaround I came up with without using the function
involving wrapping the `Registry` in an Arc and accessing `OtelData`
directly, but that led to [this bug in
tracing-subscriber](tokio-rs/tracing#2668).
Bug Report
Version
tracing-subscriber 0.3.17
Description
Here:
These lines here silently require that the inner type is a
Registry
in order to runCloseGuard
logic in sharded.rs.CloseGuard::drop
from here is the only way to callDataInner::clear
here.This results in the
DataInner
not being freed (memory leak I believe), and the parent span not having it'sref_count
decremented, leading to the parent span being stuck in limbo for eternity.I ran into this when wrapping the registry type to have it behind an
Arc
to do some OTEL shenanigans with more than 32 tracing fields.The text was updated successfully, but these errors were encountered: