<div dir="ltr">Have you looked at <a href="https://github.com/openresty/no-pool-nginx">https://github.com/openresty/no-pool-nginx</a> ?</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Aug 2, 2015 at 7:31 AM, xfeep <span dir="ltr"><<a href="mailto:nginx-forum@nginx.us" target="_blank">nginx-forum@nginx.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, Maxim,<br>
<br>
Thanks for your reply!<br>
-------------------------------------------------------<br>
<span class="">> Well, the answer is simple: nginx is not designed to be a shared<br>
> library.  If you want to convert it to be one, it's you who are<br>
> responsible for cleaning up various global allocations.<br>
><br>
<br>
</span>You're right.<br>
But for module developers who use valgrind there are maybe some confusion,<br>
the built-in core modules also have "memory leaks" , despite the fact that<br>
those are not real leaks because OS will free them after  nginx<br>
master/worker processes exit.<br>
<br>
Regards.<br>
Xfeep<br>
<br>
Posted at Nginx Forum: <a href="http://forum.nginx.org/read.php?2,260692,260704#msg-260704" rel="noreferrer" target="_blank">http://forum.nginx.org/read.php?2,260692,260704#msg-260704</a><br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
</div></div></blockquote></div><br></div>