While running the smbtorture “base.scan-pipe_number.scan-pipe_number” test against the Samba 4.18.7 release, I see that at the end of the test 96% of memory gets consumed by smbd. Only around 8% of memory was consumed before the test was run. Memory starts to get consumed when the test is complete as FDs are cleaned up. The test result is successful, but the memory usage of the smbd process spikes up which then never comes down. Server Information OS: Amazon Linux 2 RAM: 16 GiB CPU: 8 Cores.