I'm not sure this is robust enough as a test case, that's why I'm adding
it here instead of in the test caseh, but I ran smbd under valgrind
before and after the update, and less bytes were lost for the same
smbclient connection:
before:
==3977== LEAK SUMMARY:
==3977== definitely lost: 72 bytes in 7 blocks
After:
==5438== LEAK SUMMARY:
==5438== definitely lost: 24 bytes in 1 blocks
The client command was (with a suitable smb.conf and /pub directory):
smbclient //localhost/pub -U ubuntu%ubuntu -c "pwd;dir;cd dir1;dir;pwd;cd
dir11; pwd; dir; cd /; cd dir2; pwd; dir; cd /"
** Changed in: samba (Ubuntu Bionic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: samba (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1814532
Title:
Big samba memory leak fixed upstream
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1814532/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
