Memory leak in v0.154.0

[songjiaxun]

Thanks for stopping by to let us know something could be better!

PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.

Is this a client library issue or a product issue? We will only be able to assist with issues that pertain to the behaviors of this library. If the issue you're experiencing is due to the behavior of the product itself, please visit the Support page to reach the most relevant engineers.

If the support paths suggested above still do not result in a resolution, please provide the following details.

Environment details

• Programming language: golang
• OS: gcr.io/distroless/base-debian11 image
• Language runtime version: debian11
• Package version: v0.154.0

Steps to reproduce

In the GKE GCS FUSE CSI driver project, the google.golang.org/api package is used to communicate with the GCS storage API. We found that the feature feat(transport): add OpenTelemetry context propagation might introduce a memory leak.

In our project, we are using go.opentelemetry.io/otel v1.21.0, which is the same version this repo is using.

In our stress test, we found that the otelgrpc.newConfig for some reason cannot be cleaned up from the heap. Please see the heap profiling result:

As a result, our application memory consumption grows unlimitedly over the time:

After we reverted the google.golang.org/api package version back to v0.153.0, the memory usage went back to normal:

I will DM you for the detailed reproducing and profiling steps.

Making sure to follow these steps will guarantee the quickest resolution possible.

Thanks!

[codyoss]

This looks likely like the same issue described here: open-telemetry/opentelemetry-go-contrib#4226 .