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
Have a long running go routine to refresh a device auth token and was noticing a sharp increase in memory.
used pprof and idenitifed data dog's statsd buffer go keeping all the memory. More specifically, statsd.nextStatsBuffer have the max default size set for the buffer and initialize the buffer with the regular http client.
Tried forcing flush on statsd to no avail but the leak persists, any leads?
The text was updated successfully, but these errors were encountered:
I've encountered a similar situation with statsd.nextStatsBuffer steadily growing its memory footprint in a long running process that has a couple of goroutines.
v5@v5.1.1/statsd/buffer.go dominates the heap live size google/pprof@v0.0.0-20221118152302-e6195bd50e2 tops the heap live objects (with stats/buffer.go a close third)
Hi,
Have a long running go routine to refresh a device auth token and was noticing a sharp increase in memory.
used pprof and idenitifed data dog's statsd buffer go keeping all the memory. More specifically,
statsd.nextStatsBuffer
have the max default size set for the buffer and initialize the buffer with the regular http client.Tried forcing flush on statsd to no avail but the leak persists, any leads?
The text was updated successfully, but these errors were encountered: