[Samba] Samba 3.0.14 (Debian Sarge) Memory Leakage

[it]

i have a question about memory.
When I launched the "top" command, I can see the following:
top - 16:08:47 up 135 days,  6:07,  1 user,  load average: 0.00, 0.00, 0.00
Tasks:  96 total,   1 running,  95 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.3% us,  0.0% sy,  0.0% ni, 99.1% id,  0.5% wa,  0.0% hi,  0.0% si
Mem:   1036052k total,  1028580k used,     7472k free,   123376k buffers
Swap:  2000052k total,     8564k used,  1991488k free,   734732k cached

99% of my memory is used but It is impossible to see what proccess take
the amount of the memory when I see "%MEM" column

Hobbit, a monitoring tool, tells me that "physical" memory used is 99%
and "actual" memory used is 16%!!

Is somebody have explanations about this?

I know that if I stop smbd and restart it, my "physical" memory used 
raise to 0% and increase progressively.

Thanks a lot for your help in advance,

Mike

----- Original Message -----
From: Dirk Becker <dirk.becker at symeo.com>
To: Volker Lendecke <Volker.Lendecke at SerNet.DE>
Cc: it at ramadaparkhotel.ch, samba at lists.samba.org
Sent: lundi 20 novembre 2006 13 h 41 GMT+0100 Europe/Berlin
Subject: Re: [ARKSPAM] Re: Re: [Samba] Samba 3.0.14 (Debian Sarge) Memory Leakage

Volker Lendecke wrote:
> On Sun, Nov 19, 2006 at 06:43:42PM +0100, it wrote:
>> I have the same problem.
>> We are using version 3.0.14a under Debian Sarge
>> and after installing a local printer/fax HP LaserJet 3050,
>> the memory server is allocated to the user session until reaches 100%.
>> I don't know how to avoid it.
> 
> Install a different printer driver... I'm not the
> authoritative source here, but I've seen posts passed on
> this list where even MS servers have trouble with certain
> printer drivers. To make 100% sure it's a driver problem, we
> would need a debug level 10 log of a smbd chewing memory.
> This log is going to be huge, so you should put it on some
> place where we can download it.
> 
> Volker
> 

Since my upgrade to 3.0.23c the mentioned problems seem to be gone.
Nevertheless I will remove samba printers and stop cups support on the
misbehaving server as we do not depend on this service. I will then go
back to 3.0.14 and see if the problem persists.
Unfortunately I cannot let samba run under valgrind on this server
because it is a production system. Perhaps I can try to produce the
memory leakage on a test system.

Thanx for helping so far

Dirk