Unbounded memory usage

I’m noticing issues where Node processes consuming histograms (and surprisingly) meters are growing memory in a linear, unbounded fashion. Removing measured fixes this issue. I’m not very surprised that histograms are memory-hungry given they’re backed by a binary heap, I am much more surprised the meters seem to be as well.

Is this something you’ve encountered before?

[jondot]

Update: the thing is, that if you use meters (which use a timer to periodically aggregate the data), and then you swap them periodically to avoid a meter going out of range - you get dangling timers.

In addition if you use many meters, let’s say 100 in an app, then you have 100 timers running - does that affect performance?

[fieldju]

I know I already closed this issue. Just incase anyone finds themselves here.

My suspicion based on some of the comments above. Is that users where creating Meters regularly and not managing their lifecycles properly.

When a Meter is created you must call Meter.end() when you are done with it. The end method clears the interval which would allow the garbage collector to fully destroy the object.

When you use the Collection or Self Reporting Metrics Registry, shutdown methods to properly end their and the registered metrics lifecycle are exposed. SelfReportingMetricsRegistry#shutdown, Collection#end