Bug#558453: [Pkg-samba-maint] Bug#558453: Bug#558453: 558453: samba memory leak (3.4.3 backport)
Certainly. However, we (pkg maintainers) are not really in position to help that much here, except by acting as proxies with upstream. Are you in position to report this in upstream's Bugzilla (https://bugzilla.samba.org) so that you can investigate this deeper directly with them? I have to say: WOW.. Upstream bug #7020, which you opened, is really impressive and I wanted to thank you publicly for the great cooperation you have with upstream in investigating it. I'll be more than happy to close #558453 when we release 3.4.4 packages. signature.asc Description: Digital signature
Bug#558453: [Pkg-samba-maint] Bug#558453: 558453: samba memory leak (3.4.3 backport)
On Sun, 2010-01-03 at 08:30 +0100, Christian PERRIER wrote: Quoting Ross Boylan (rossboy...@stanfordalumni.org): I also encountered severe memory leak in samba 3.4 backported to lenny. I backported by compiling from source, pulling in various sid dependencies as needed. I installed with # dpkg -i samba-common_3.4.3-1_all.deb samba-common-bin_3.4.3-1_i386.deb samba-doc-pdf_3.4.3-1_all.deb samba_3.4.3-1_i386.deb libsmbclient_3.4.3-1_i386.deb smbclient_3.4.3-1_i386.deb Within 2 days smbd had consumed over 2G of memory, bringing the system to a crawl. Unfortunately, other processes got killed by the kernel. I realize this is not a supported configuration, but thought it was worth a report. Certainly. However, we (pkg maintainers) are not really in position to help that much here, except by acting as proxies with upstream. Are you in position to report this in upstream's Bugzilla (https://bugzilla.samba.org) so that you can investigate this deeper directly with them? I just opened https://bugzilla.samba.org/show_bug.cgi?id=7020. Oddly, I didn't find any similar reports in samba's bugzilla, except for something about valgrind leaks that I think were fixed earlier. Nor did the samba list have such reports in the last few months. It would also be good if someone could check a similar situation with an unstable machine. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538819 includes a report for 3.4.2 in testing. I'm short on time, and thought I was going to punt and revert to 3.2. Since I've found that the 3.2-3.4 transition is one way, I've reinstalled my 3.4 debs. I also saw this bug right under my nose during a Vista file based backup. This presumably generates lots of file writes to the share; over the course of the backup smbd memory use rose to 1.85G, 1.57G of which was resident. I exited/shut down lots of stuff so my system didn't get zapped (it has 2G physical RAM and 2G swap, i386 architecture). Restarting the server eliminated the giant process. BTW, if anyone has info about how to downgrade to 3.2, that would be great, as 3.4 isn't really useable for me with this bug. A solution that involved recreating all the databases would be fine, as I only have a few passwords in there. Ross -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558453: 558453: samba memory leak (3.4.3 backport)
I also encountered severe memory leak in samba 3.4 backported to lenny. I backported by compiling from source, pulling in various sid dependencies as needed. I installed with # dpkg -i samba-common_3.4.3-1_all.deb samba-common-bin_3.4.3-1_i386.deb samba-doc-pdf_3.4.3-1_all.deb samba_3.4.3-1_i386.deb libsmbclient_3.4.3-1_i386.deb smbclient_3.4.3-1_i386.deb Within 2 days smbd had consumed over 2G of memory, bringing the system to a crawl. Unfortunately, other processes got killed by the kernel. I realize this is not a supported configuration, but thought it was worth a report. I've gone back to lenny, even though that is giving me excessive (15--20%) CPU useage. My only client is a Vista laptop. It did not have the HP toolbox installed (although I have installed it today). I am not using samba as a domain controller, just file and print services. Printing, which is the part generating the high CPU, is via CUPS. Ross Boylan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558453: [Pkg-samba-maint] Bug#558453: 558453: samba memory leak (3.4.3 backport)
Quoting Ross Boylan (rossboy...@stanfordalumni.org): I also encountered severe memory leak in samba 3.4 backported to lenny. I backported by compiling from source, pulling in various sid dependencies as needed. I installed with # dpkg -i samba-common_3.4.3-1_all.deb samba-common-bin_3.4.3-1_i386.deb samba-doc-pdf_3.4.3-1_all.deb samba_3.4.3-1_i386.deb libsmbclient_3.4.3-1_i386.deb smbclient_3.4.3-1_i386.deb Within 2 days smbd had consumed over 2G of memory, bringing the system to a crawl. Unfortunately, other processes got killed by the kernel. I realize this is not a supported configuration, but thought it was worth a report. Certainly. However, we (pkg maintainers) are not really in position to help that much here, except by acting as proxies with upstream. Are you in position to report this in upstream's Bugzilla (https://bugzilla.samba.org) so that you can investigate this deeper directly with them? It would also be good if someone could check a similar situation with an unstable machine. signature.asc Description: Digital signature
