Possible samba4 / winbind memory leak?

[Ricky Nance]

(Sorry shift enter apparently sends emails in gmail...)

instead of:

p talloc_report_full(0, stderr)

then run:

tar --xz -cf leak.tar.xz /tmp/leak.txt

if you email it. (it will compress it a lot).

Ricky


On Tue, Apr 2, 2013 at 7:43 AM, Ricky Nance <ricky.nance at weaubleau.k12.mo.us
> wrote:

> Andrew W.,
>
> When I was running into memory leaks I had a cron job (it emailed me) that
> ran ps_mem.py ( http://www.pixelbeat.org/scripts/ps_mem.py )* *every hour
> and redirected it into a file. The bash script I ran looked like this...
>
> #/bin/bash
> date >> /sambamem.txt && ps_mem.py | grep 'samba\|smbd' >> /sambamem.txt
>
>
> also, its probably easier to get the output running:
>
> p talloc_report_full(0, fopen("/tmp/leak.txt", "w")
>
> instead of
>
>
>
> On Tue, Apr 2, 2013 at 4:04 AM, Andrew Walters <
> aw-sambalists at silverstream.net.nz> wrote:
>
>>
>> ----- Original Message -----
>> > From: "Andrew Bartlett" <abartlet at samba.org>
>>
>> > There are still ways to debug this, if you still have the process
>> > around.  Ricky Nance (CC'ed) is the expert in this, so I've CC'ed
>> > him.
>> >
>> > Essentially, what we need you to do is attach with gdb:
>> >
>> > gdb -p <pid>
>> >
>> > and then get me:
>> >
>> > bt full
>> >
>> > (because if it isn't responding to a sigkill, then it will be in an
>> > infinite loop somewhere, and we want to know where that is).
>> >
>> > Then you run:
>> >
>> > p talloc_report_full(0, stderr)
>> >
>>
>> I killed it, sorry. It'll take a couple of days to get it back in that
>> state. When it is, I'll run and send you as above.
>>
>>
>> Thanks,
>>
>> Andrew W
>>
>
>
>
> --
>
>


--