[BUG]: OOM in BatchSpanProcessor

[50U10FCA7]

What happened?

OOM in trace::span_processor_with_async_runtime::BatchSpanProcessor:

opentelemetry-rust/opentelemetry-sdk/src/trace/span_processor_with_async_runtime.rs

Line 236 in dac8bd5

self.spans.push(span);

.

BatchSpanProcessor adds a span to already overloaded batch which leads to OOM.

Not tested on sync version, but seems like the problem related to both sync and async:

opentelemetry-rust/opentelemetry-sdk/src/trace/span_processor.rs

Line 464 in dac8bd5

spans.push(span);

OpenTelemetry API Version / SDK version

Latest release:

opentelemetry = "0.28"
opentelemetry_sdk = "0.28"
opentelemetry-otlp = "0.28"

What Exporter(s) are you seeing the problem on?

OTLP

Relevant log output

Here's the MRE demonstrating the problem: https://github.com/50U10FCA7/otel-oom

P.S. Please fix your "Bug Report" GitHub template:

[cijothomas]

Looks like an issue with BatchSpanProcessor. LogProcessor don't face this issue.

[cijothomas]

@50U10FCA7 Would you be interested in contributing a fix? The BatchLogProcessor can be used as a reference. (if you notice the issue in BatchLogProcessor too, then please do report it)

[50U10FCA7]

@cijothomas

Would you be interested in contributing a fix?

Sure, will fix this. Seems like we just need to check the batch is not overloaded before inserting new spans/messages to it.

[50U10FCA7]

Not a bug, problem caused by a custom runtime with unbounded channel for sending spans. See #2793 (comment)

Closing this one.