Re: [Wrapper-user] wrapper 3.5.25 memory leak on CentOS 7

[Tim L. <tim...@gm...>]

There are two bugs at play here. One is in glibc, the other in the wrapper
itself.

- glibc leak:
https://sourceware.org/bugzilla/show_bug.cgi?id=17370
It is fixed in newer releases of glibc, so if you can upgrade your glibc
libraries please do so.

If you can not upgrade your glibc libraries, see patch
02.workaround-memory-leak-in-ftell.

- wrapper leak:
I've also attached a fix for the memory leak in logging in the wrapper
itself in patch 01.fixes-memory-leak-in-error-logging.
It uses the same solution as the windows version to prevent using up all
the memory.

Regards,
Tim


On Sun, Nov 16, 2014 at 11:51 AM, Aleksey Chudov <ale...@gm...>
wrote:

> Finally I found that memory leak relates to wrapper.logfile options. As
> soon as I comment the following options in configuration file the
> problem goes away.
>
> wrapper.logfile=/var/log/myapp.log
> wrapper.logfile.format=LPTM
> wrapper.logfile.loglevel=INFO
> wrapper.logfile.maxsize=100m
> wrapper.logfile.maxfiles=10
>
> After enabling options one by one I found two problem options. As soon
> as I uncomment the following options wrapper starts to eat memory.
>
> wrapper.logfile.maxsize=100m
> wrapper.logfile.maxfiles=10
>
> I can reproduce the problem.
>
>
> Regards,
> Aleksey
>
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>