[Bug 280671] Memory leak on FreeBSD 13.3 and 14.1
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 280671] Memory leak on FreeBSD 13.3 and 14.1"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 10 Aug 2024 17:48:03 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280671 --- Comment #5 from sre@truespeed.com --- Hi Mark Thanks for looking into this issue! I'll try and provide all the detail I can. Today is the 3rd day the Server's been running so it was likely to run into that state, and it has! I've captured the requested stats in two scenarios: - At the point of "minimum" available memory (just prior to when I would expect it to start thrashing) - After I've killed most of the running processes and jails (to see what's still hogging it) sysctl_vmstats_thrashing.txt and vmstat_thrashing.txt show the stats before I intervene. stopped_sysctl_vmstats_thrashing.txt and stopped_vmstat_thrashing.txt show the stats after I've killed most of the running processes. I've attached two more charts showing the last 12 hours before intervention for Total Memory and Memory Types. To answer your question about Memory loss, we "lost" 1.5GB of Total Memory over a ~9 hour period before I intervened and rebooted the box. (93.6GB usually, and slowly dropped to 92.1GB) The total memory didn't return to usual after I killed processes, only after a reboot, and looking at the charts it reduced further after I killed processes. This was the top memory profile after I killed everything. Mem: 1691M Active, 859M Inact, 64G Laundry, 4495M Wired, 22G Free ARC: 2470M Total, 1530M MFU, 720M MRU, 7936K Anon, 20M Header, 192M Other 2021M Compressed, 5712M Uncompressed, 2.83:1 Ratio Thanks again, if there's anything else I can provide please let me know. SRE -- You are receiving this mail because: You are the assignee for the bug.