Created attachment 16561 [details] Excerpt from talloc report On a heavily loaded Samba printserver with several hundred queque it was noted that after upgrading from 4.6 to 4.13 smbd processes were eating up memory over the cause of a few days. As an example the smbd process with the highest resided set size was PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 7657 WIN\pet+ 20 0 1369160 398484 7824 S 0,0 2,5 1:02.80 smbd 398 MB... talloc report of the process: full talloc report on 'null_context' (total 153473847 bytes in 2253252 blocks) 153 MB.... The talloc report has a myriad duplicate printer related metadata objects. The talloc report is 2M lines, still grinding through it. Looking...
This bug was referenced in samba master: 4c3fb2a5912966a61e7ebdb05eb3231a0e1d6033 481176ec745c14b78fca68e01a61c83405a4b97b 12f516e4680753460e7fe8811e6c6ff70057580c
Created attachment 16575 [details] Patch for 4.13 and 4.14 cherry-picked from master
Pushed to autobuild-v4-{14,13}-test.
This bug was referenced in samba v4-14-test: 55c76604ca2fac7348a6bddba1dfdc128c728f30 ed30ce7aa0cce39bf0e0a6a97afc8716873692fc e85d111f54f7aa77803f1e9fef92d5dd97968fd9
This bug was referenced in samba v4-13-test: 890cc945e338bbe3047bee45772330ec32feb5a2 85b5657cbd685968045fcaad2e7d3323b902edc9 3644afc38c726a19f39f1d4f96badfb7827fb1a4
This bug was referenced in samba master: 1efa9ffd7ae77ebf22b28c12dd642a89991b75d2
Created attachment 16587 [details] Additional patch for 4.13 and 4.14, cherry-picked from master Additional patch for 4.13 and 4.14
(In reply to Samuel Cabrero from comment #7) Pushed to autobuild-v4-{14,13}-test.
This bug was referenced in samba v4-13-test: 2022e490d5e506b5b07b02578a68b124241bdad6
This bug was referenced in samba v4-14-test: b74a079a202089644090094dac06d327ff31aeec
This bug was referenced in samba v4-14-stable (Release samba-4.14.3): 55c76604ca2fac7348a6bddba1dfdc128c728f30 ed30ce7aa0cce39bf0e0a6a97afc8716873692fc e85d111f54f7aa77803f1e9fef92d5dd97968fd9 b74a079a202089644090094dac06d327ff31aeec
Closing out bug report. Thanks!
This bug was referenced in samba v4-13-stable: 890cc945e338bbe3047bee45772330ec32feb5a2 85b5657cbd685968045fcaad2e7d3323b902edc9 3644afc38c726a19f39f1d4f96badfb7827fb1a4 2022e490d5e506b5b07b02578a68b124241bdad6