Memory leaks when used as a shared library

[Lord Nynex]

Have you looked at https://github.com/openresty/no-pool-nginx ?

On Sun, Aug 2, 2015 at 7:31 AM, xfeep <nginx-forum at nginx.us> wrote:

> Hi, Maxim,
>
> Thanks for your reply!
> -------------------------------------------------------
> > Well, the answer is simple: nginx is not designed to be a shared
> > library.  If you want to convert it to be one, it's you who are
> > responsible for cleaning up various global allocations.
> >
>
> You're right.
> But for module developers who use valgrind there are maybe some confusion,
> the built-in core modules also have "memory leaks" , despite the fact that
> those are not real leaks because OS will free them after  nginx
> master/worker processes exit.
>
> Regards.
> Xfeep
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,260692,260704#msg-260704
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20150804/f82a27d6/attachment.html>