Rare hang when using otlp exporter. Cause seems to be grpc using abseil sync primitives on Windows.

[malkia]

** Describe your environment **

• Windows 10/11, Visual Studio 2022, bazel 8.2.1 (bazel 8+ should work, maybe even 7+)

Steps to reproduce

• Repro steps in here https://github.com/malkia/grpc_absl_hang

What is the expected behavior?

• Using opentelemetry-cpp (through grpc) should not hang.

What is the actual behavior?

• It hangs instead, roughly 1 in 3000 cases.

Additional context
The issue is not really opentelemetry-cpp, but more like gRPC using abseil primitives on Windows, though users relying on the otlp grpc exported may be affected.

[dbarker]

Thanks for reporting this and sharing the code to reproduce the issue. The code shared will create otlp grpc logs and metrics exporters instantiated with their own grpc clients.

Is sharing a single grpc client (described here) doable and a potential workaround for the issue?

[malkia]

@dbarker Initially these were set to both 4317, this was just to ensure this was not actually causing it, but it didn't matter.

[dbarker]

@dbarker Initially these were set to both 4317, this was just to ensure this was not actually causing it, but it didn't matter.

Makes sense on the port. I was just curious about the configuration of the exporters and if explicitly creating a single OtlpGrpcClient instance and sharing might be a workaround assuming the sync issue is between two OtlpGrpcClient instances.

[github-actions]

This issue was marked as stale due to lack of activity.