From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <a.bokovoy@sam-solutions.net>
Date: Thu, 4 Oct 2001 12:00:38 +0300
From: Alexander Bokovoy <a.bokovoy@sam-solutions.net>
To: sisyphus@altlinux.ru
Message-ID: <20011004120038.A15613@pc152.belcaf.minsk.by>
Mail-Followup-To: sisyphus@altlinux.ru
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.3.22.1i
Subject: [sisyphus] [tpot@samba.org: Re: Winbindd Memory Leak]
Sender: sisyphus-admin@altlinux.ru
Errors-To: sisyphus-admin@altlinux.ru
X-BeenThere: sisyphus@altlinux.ru
X-Mailman-Version: 2.0
Precedence: bulk
Reply-To: sisyphus@altlinux.ru
List-Help: <mailto:sisyphus-request@altlinux.ru?subject=help>
List-Post: <mailto:sisyphus@altlinux.ru>
List-Subscribe: <http://altlinux.ru/mailman/listinfo/sisyphus>,
	<mailto:sisyphus-request@altlinux.ru?subject=subscribe>
List-Id: <sisyphus.altlinux.ru>
List-Unsubscribe: <http://altlinux.ru/mailman/listinfo/sisyphus>,
	<mailto:sisyphus-request@altlinux.ru?subject=unsubscribe>
List-Archive: <http://altlinux.ru/pipermail/sisyphus/>
Archived-At: <http://lore.altlinux.org/sisyphus/20011004120038.A15613@pc152.belcaf.minsk.by/>
List-Archive: <http://lore.altlinux.org/sisyphus/>

Можно надеяться, что дырка, в которую утекает память в Winbindd,
будет закрыта еще до выхода 2.2.2. По крайней мере, причина утекания
обнаружена.

----- Forwarded message from Tim Potter <tpot@samba.org> -----

Date: Thu, 4 Oct 2001 09:32:57 +1000 (EST)
From: Tim Potter <tpot@samba.org>
To: "Esh, Andrew" <AEsh@tricord.com>,
	"Samba-Technical (E-mail)" <samba-technical@lists.samba.org>
Subject: Re: Winbindd Memory Leak

Tim Potter writes:

> > The size of the leak varies from 8 to 12 bytes, but the stack
> > is always identical. The call to talloc implies that all of
> > this leaked memory could be freed at one point by calling
> > talloc_destroy. My problem is, I don't know (yet) where to do
> > that. The obvious place is somewhere in the stack listed
> > above, but I don't quite see where yet.
> 
> There is a call to lp_talloc_free() in the winbindd main loop
> which should free memory as it is going along.  This only frees
> memory from the global tdb used for parameter strings.  I suspect
> there is another TALLOC_CTX that is being used, probably in the
> rpc code, that is not being freed.  I'm taking a look at it now.

Jeremy and I have decided to do a bit of refactoring (i.e
chainsaw work) on connection and memory management in winbind.
It may make it in to 2.2.


Tim.

----- End forwarded message -----

-- 
/ Alexander Bokovoy
$ cat /proc/identity >~/.signature
  `Senior software developer and analyst for SaM-Solutions Ltd.`
---
Only a fool has no doubts.