Details
-
Bug
-
Resolution: Done
-
Major
-
26.1.1.Final
-
None
Description
When migrating from opentracing to opentelemetry, we checked out the available API and found a problematic code snippet that causes a memory leak. (pretty much the same as in this issue: https://issues.redhat.com/browse/WFLY-16256)
We are using WildFly 26.1.1.Final.
This time around it's even worse because a new instance is created with every request done with a traced client, and there is no way to disable the tracing since the filter is added automatically.
Here is a Screenshot of a heap dump. Almost all of the 130 007 elements are contextual instances containing the same OpenTelemetrySdk.