AW: winbind 3.3.7 memory usage

[Dr. Hansjoerg Maurer]

Hi

If run winbind with valgrind for 4 days no
One winbind (PID 14762) grows up to 727/448 MByte VSZ/RSS
 
[root at donau ~]# psgrep winbind
root     11749  0.1  5.7 394492 119072 ?     Ss   Oct01  10:09 valgrind --tool=memcheck --leak-check=full -v --num-callers=20 --trace-children=yes winbindd
root     11806  0.0  3.0 351088 62516 ?      S    Oct01   0:05 valgrind --tool=memcheck --leak-check=full -v --num-callers=20 --trace-children=yes winbindd
root     11807  0.0  3.2 357580 67176 ?      S    Oct01   0:06 valgrind --tool=memcheck --leak-check=full -v --num-callers=20 --trace-children=yes winbindd
root     12053  0.0  3.3 355820 68288 ?      S    Oct01   0:14 valgrind --tool=memcheck --leak-check=full -v --num-callers=20 --trace-children=yes winbindd
root     12054  0.0  4.5 370644 92540 ?      S    Oct01   0:39 valgrind --tool=memcheck --leak-check=full -v --num-callers=20 --trace-children=yes winbindd
root     14502  0.2  5.0 393100 104816 ?     S    Oct01  15:04 valgrind --tool=memcheck --leak-check=full -v --num-callers=20 --trace-children=yes winbindd
root     14762  6.6 21.8 727332 448924 ?     R    Oct01 371:14 valgrind --tool=memcheck --leak-check=full -v --num-callers=20 --trace-children=yes winbindd


The valgrind output has a uncompressed size of 440 MByte's (compressed 4 MByte) 
therefore I put it to
ftp://ftp.dlr.de/robotic/outgoing/maurerh/valgrind.out.bz2

Regards

Hansjörg














----- Originalnachricht -----
Von: Volker Lendecke <Volker.Lendecke at SerNet.DE>
Gesendet: Don, 1.10.2009 10:29
An: Dr. Hansjoerg Maurer <hansjoerg.maurer at itsd.de>
Cc: samba-technical at lists.samba.org
Betreff: Re: winbind  3.3.7 memory usage

On Thu, Oct 01, 2009 at 10:18:54AM +0200, Dr. Hansjoerg Maurer wrote:
> yes, no problem, we have a box where this should be no problem.
> Can you point me to a short howto, how I can do this?

Install debugging symbols. Either your distro should bring
samba debuginfo packages, or if you compile it yourself,
compile with -g. ./configure --enable-developer for example
does that.

Install valgrind (www.valgrind.org or your distro repo).
Then start winbind as follows (all in one line of course):

valgrind --tool=memcheck --leak-check=full -v
--num-callers=20 --trace-children=yes winbindd >
/tmp/valgrind.out 2>&1 

The resulting processes will be larger from the start. If
after a while one subprocess has grown substantially, shut
down winbind with

smbcontrol <pid> stop

The output of /tmp/valgrind.out is the interesting piece
then.

Volker