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
I think the current behavior is to create a new timer each time telemetry is accepted by the backend. By default, Only 4 of these timers should be created per minute (default batch interval is 15 seconds), and they should be cleared every _resendInterval, which is 1 minute. If you turn off batching, I would imagine they would pile up for each send and disappear after the minute passes.
All of the extra timers are redundant after the 1st one, and so I will make a change to not create new ones after the 1st
Hi App insights team,
I'm trying to identify a memory leak in one of our apps.
Please see the below screenshot
Comparing the two memory dumps, seems that there are many closures being added to the memory from this line of code.
https://github.com/microsoft/ApplicationInsights-node.js/blob/develop/Library/Sender.ts#L138
Quickly commenting out that line of code seems to fix the problem.
What are your thoughts about this?
Thanks!
The text was updated successfully, but these errors were encountered: