Samba4 and memory consumption - needing frequent kills

[Andrew Bartlett]

On Thu, 2012-08-09 at 17:08 +1000, Andrew Bartlett wrote:
> On Wed, 2012-08-08 at 21:04 +0200, Arvid Requate wrote:
> > Hello Kev,
> > 
> > maybe you are facing the same issue here as reported in 
> > https://bugzilla.samba.org/show_bug.cgi?id=8827 ?
> 
> As I've just commented on the bug, I need a --leak-report-full rather
> than just --leak-report.
> 
> Also, if that does not show the cause, perhaps instead of shutting down
> the server run with --leak-report-full, then attach to the large process
> with:

Given the issues with the memory dumps being repeated in overwealming
detail, here is a new instruction:

Run samba as:

gdb --args samba -M single --leak-report

Then:

run

When it becomes large, run 

p talloc_report_full(0, stderr)

and mail me *only* the output of that command, not the earlier or later output.  

The issue with the previous logs is that the same allocation (present in
multiple forked children) was being logged multiple times, as each child
exited.  This caused the massive log buildup, without giving me much
more information. 

You may replace stderr with a file on disk with something like:

p talloc_report_full(0, fopen("/tmp/leak.txt", "w")

Hopefully this will give you and me the information we need.

Andrew Bartlett

-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org