Issue in cento version 2.5.251210

Hi Team,

We are continuously observing mlx stopped getting traffic on queues and cento is taking automatic restart due to kernel level OOM kill. I remember there was a bug which was causing memory leaks. Can you please help me out with this issue.

Apr 25 07:49:26 ams7nprobe03 systemd[1]: cento.service: A process of this unit has been killed by the OOM killer.
Apr 25 07:49:58 ams7nprobe03 systemd[1]: cento.service: Main process exited, code=killed, status=9/KILL
Apr 25 07:49:58 ams7nprobe03 systemd[1]: cento.service: Failed with result 'oom-kill'.
Apr 25 07:49:58 ams7nprobe03 systemd[1]: cento.service: Consumed 1month 3d 9h 6min 37.956s CPU time.
Apr 25 07:50:04 ams7nprobe03 systemd[1]: cento.service: Scheduled restart job, restart counter is at 1.
Apr 25 07:50:04 ams7nprobe03 systemd[1]: Stopped 100Gbps NetFlow v5/v9/IPFIX probe for IPv4/v6.
Apr 25 07:50:04 ams7nprobe03 systemd[1]: cento.service: Consumed 1month 3d 9h 6min 37.956s CPU time.
Apr 25 07:50:04 ams7nprobe03 systemd[1]: Starting 100Gbps NetFlow v5/v9/IPFIX probe for IPv4/v6...
Apr 25 07:50:04 ams7nprobe03 systemd[1]: Started 100Gbps NetFlow v5/v9/IPFIX probe for IPv4/v6.

root@ams7nprobe03:/etc/cento# tail -f /opt/data/nProbe/temp/traffic_rate.txt
mlx:mlx5_1@0 3.01 Gbps
mlx:mlx5_1@1 2.60 Gbps
mlx:mlx5_1@2 2.05 Gbps
mlx:mlx5_1@3 3.03 Gbps
mlx:mlx5_1@4 2.01 Gbps
mlx:mlx5_1@5 2.13 Gbps
mlx:mlx5_1@6 2.96 Gbps
mlx:mlx5_1@7 2.16 Gbps
mlx:mlx5_1@8 0.00 Gbps
mlx5_sum: 19.95
^C
root@ams7nprobe03:/

Start by reviewing the cento.service OOM-kill logs and monitoring /opt/data/nProbe/temp/traffic_rate.txt, especially the mlx5_1@8 queue. Reproduce or correlate the stopped queue with memory growth and the automatic restart; done means identifying the leak or failure cause and confirming that cento no longer reaches an OOM kill.