Open VivekSubr opened 1 week ago
What's your version of otel-cpp and do you enable async exporting?
There was a thread safety problem before 1.10.0 in OTLP HTTP exporter when otel-cpp is built without async export(Without -DENABLE_ASYNC_EXPORT
or WITH_ASYNC_EXPORT_PREVIEW
).
@owent - 1.15, haven't enabled async exporting... is async export still in preview in 1.15?
@owent - 1.15, haven't enabled async exporting... is async export still in preview in 1.15?
gRPC async exporting is still in preview.
Does this problem happens when shuting down? Do you compile both otel-cpp and proto as dynamic library?Just wondering why the destructor of RepeatedPtrField<opentelemetry::proto::trace::v1::ResourceSpans>
is in gRPC exporter.
It's HTTP exporter, and proto is from yum install.
We're investigating if it's memory corruption from somewhere else.
It's HTTP exporter, and proto is from yum install.
We're investigating if it's memory corruption from somewhere else.
Do you mean protobuf? I reviewed the codes and found the messages and arena will not leave the scope of OtlpHttpExporter::Export
in my understanding.
I found another crash in #2982 when using metrics and timeout happens. Not sure if it relates this one.
Describe your environment Built and running on linux,
Protobuf version installed - 3.17.3
Steps to reproduce Don't have exact steps to reproduce, happens intermittently.
Backtrace
Additional Info
Crash appears to be on destruction of arena object in, https://github.com/open-telemetry/opentelemetry-cpp/blob/main/exporters/otlp/src/otlp_http_exporter.cc#L102
It's not apparent why this might happen... any help will be appreciated.