Running:
smbclient //localhost/pub -U ubuntu%ubuntu -c "pwd;dir;cd dir1;dir;pwd;cd dir11; pwd; dir; cd /; cd dir2; pwd; dir; cd /"
Server valgrind report:
==3887== LEAK SUMMARY:
==3887== definitely lost: 72 bytes in 7 blocks
==3887== indirectly lost: 0 bytes in 0 blocks
==3887== possibly lost: 125,212 bytes in 488 blocks
==3887== still reachable: 117,607 bytes in 901 blocks
==3887== suppressed: 0 bytes in 0 blocks
After update:
==7133== LEAK SUMMARY:
==7133== definitely lost: 24 bytes in 1 blocks
==7133== indirectly lost: 0 bytes in 0 blocks
==7133== possibly lost: 125,212 bytes in 488 blocks
==7133== still reachable: 117,607 bytes in 901 blocks
==7133== suppressed: 0 bytes in 0 blocks
I was hoping the original reported would have tried the updated packages, since he seemed quite affected by this memleak. But in the meantime, this is the verification I can do.
With the bionic packages:
*** 2:4.7.6+ dfsg~ubuntu- 0ubuntu2. 6 500 br.archive. ubuntu. com/ubuntu bionic-updates/main amd64 Packages
500 http://
Running:
smbclient //localhost/pub -U ubuntu%ubuntu -c "pwd;dir;cd dir1;dir;pwd;cd dir11; pwd; dir; cd /; cd dir2; pwd; dir; cd /"
Server valgrind report:
==3887== LEAK SUMMARY:
==3887== definitely lost: 72 bytes in 7 blocks
==3887== indirectly lost: 0 bytes in 0 blocks
==3887== possibly lost: 125,212 bytes in 488 blocks
==3887== still reachable: 117,607 bytes in 901 blocks
==3887== suppressed: 0 bytes in 0 blocks
After update:
==7133== LEAK SUMMARY:
==7133== definitely lost: 24 bytes in 1 blocks
==7133== indirectly lost: 0 bytes in 0 blocks
==7133== possibly lost: 125,212 bytes in 488 blocks
==7133== still reachable: 117,607 bytes in 901 blocks
==7133== suppressed: 0 bytes in 0 blocks
I was hoping the original reported would have tried the updated packages, since he seemed quite affected by this memleak. But in the meantime, this is the verification I can do.