[Samba] Memory leak in winbindd

Noel Kelly nkelly at tarsus.co.uk
Wed Mar 20 06:01:07 GMT 2002


I have been running the CVS code for SAMBA_2_2 (2.2.4 pre) from AM Tuesday
19th since last night.  We have not had one crash but unfortunately the
winbindd process over the fifteen hour period managed to consume 290Mb of
RAM!  

I have restarted now and will keep a closer eye on memory.

Noel

-----Original Message-----
From: jra at samba.org [mailto:jra at samba.org]
Sent: 14 March 2002 04:13
To: Ken Cross
Cc: 'Noel Kelly'; samba at lists.samba.org
Subject: Re: [Samba] Memory leak in winbindd


On Wed, Mar 13, 2002 at 08:12:26AM -0500, Ken Cross wrote:
> Noel:
> 
> There's definitely a memory leak (try the little script at the bottom
> and it's obvious -- the wbinfo -t does it).  
> 
> I'm not certain that the memory leak causes it to die or not.  Actually,
> on my system it isn't dead -- it just doesn't return user/group data any
> more.  wbinfo -t works, but not wbinfo -u.  I think the memory leak
> fixed in 2.2.3 was in smbd not winbind, wasn't it?

I've just fixed a bug in SAMBA_2_2 CVS that could cause winbindd
to core dump on a lookup name/sid returning SID_NAME_UNKNOWN.

If you could cvs checkout this branch and see if it fixes the
winbindd dying problem I'd appreciate it.

Thanks,

	Jeremy.




More information about the samba mailing list