You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Memory Leak (global handles) when passing null as opaque argument to produce() #1127
We're seen a memory leak passing null as the opaque argument to produce.
This was subtle and tough to debug, and is quite surprising behavior.
I think the 5th argument check should also include !IsNull much like the 4th argument.
Otherwise, global (persistent) handles are leaked wrapping a null value, which doesn't make sense.
changed the title [-]Memory Leak (global handles) when passing null as opaque to produce()[/-][+]Memory Leak (global handles) when passing null as opaque argument to produce()[/+]on May 3, 2025
We also confirmed the memory leak occurs when an empty string ("") is passed for the opaque argument. This was discovered because opaque is before the headers argument we use for tracing propagation.
Activity
[-]Memory Leak (global handles) when passing null as opaque to produce()[/-][+]Memory Leak (global handles) when passing null as opaque argument to produce()[/+]Diamondlord commentedon Nov 3, 2025
We also confirmed the memory leak occurs when an empty string ("") is passed for the
opaqueargument. This was discovered because opaque is before theheadersargument we use for tracing propagation.