Bug 15486 - The smbtorture test scan-pipe_number is triggering high memory usage
Summary: The smbtorture test scan-pipe_number is triggering high memory usage
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.18.7
Hardware: x64 Linux
: P5 major (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-04 15:46 UTC by Rakesh Roshan
Modified: 2025-10-24 17:11 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rakesh Roshan 2023-10-04 15:46:02 UTC 
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.
Comment 1 roland 2025-10-24 17:11:41 UTC 
what exactly does scan-pipe_number test do? i did not manage to find that out via reading manpage or searching trough the samba git. 

i'm asking because i'd like to know if there perhaps is a relation to https://bugzilla.samba.org/show_bug.cgi?id=15261