Memory leak in NewBatchSpanProcessor following upgrade to v1.18.0 #5410
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
/kind bug
What steps did you take and what happened:
We are experiencing a strange memory leak with capz controller after upgrading to v1.18.0. We enabled pprof and saw that
trace.NewBatchSpanProcessor
memory usage is constantly growing. We can see from the call graph thatARMClientOptions
is callingOLTPTracerProvider
which in turn calls the abovementioned method. Please see pprof trace heap3.zip.We also get periodic errors in the logs, perhaps it's connected:
Note that we disabled tracing entirely.
Anything else you would like to add:
Slack thread: https://kubernetes.slack.com/archives/CEX9HENG7/p1738688304962559
capz-controller-manager deployment
Environment:
kubectl version
): Client Version: v1.31.3, Kustomize Version: v5.4.2, Server Version: v1.30.8-gke.1162000/etc/os-release
): cos-113-18244-236-77 w Docker v24.0.9 and containerd v1.7.24The text was updated successfully, but these errors were encountered: