Memory leak observed in te_stats_collector in te_dp

[sanathpholla]

Describe the bug

When TE was started for 8000 VIPs, a steady memory increase was observed in te_dp machine. This resulted in OOM Kill after 8-10 hours of starting traffic.

Feb 17 13:04:12 Client-1 kernel: [50800339.249733] Out of memory: Kill process 10409 (te_stats_collec) score 878 or sacrifice child
Feb 17 13:04:12 Client-1 kernel: [50800339.250768] Killed process 10409 (te_stats_collec) total-vm:8515812kB, anon-rss:7538392kB, file-rss:0kB, shmem-rss:0kB
Feb 17 13:04:12 Client-1 kernel: [50800339.583239] oom_reaper: reaped process 10409 (te_stats_collec), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

Feb 17 13:03:56 Client-1 kernel: [50800323.344583] [ pid ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name
Feb 17 13:03:56 Client-1 kernel: [50800323.344677] [10409]     0 10409  2128953  1885090 16920576   186781             0 te_stats_collec
Feb 17 13:03:56 Client-1 kernel: [50800323.344679] [18859]     0 18859    21296     8823   217088     3184             0 te_dp
Feb 17 13:03:56 Client-1 kernel: [50800323.344680] [18861]     0 18861    20080     9250   212992     1828             0 te_dp
Feb 17 13:03:56 Client-1 kernel: [50800323.344682] [18863]     0 18863    21101     8297   208896     3704             0 te_dp
Feb 17 13:03:56 Client-1 kernel: [50800323.344683] [20156]     0 20156    23207      453   221184      212             0 sshd
Feb 17 13:03:56 Client-1 kernel: [50800323.344685] [25403]     0 25403  2128953  1885108 16908288   186781             0 te_stats_collec

Reproduction steps

1.Send traffic to 8000 VS VIPs
2.Every 15 mins, a increase of 15MB of memory was observed.

Expected behavior

te_stat_collector should free up memory after every allocation of memory.

Additional context

No response