Memory leaks when used as a shared library

xfeep nginx-forum at
Sun Aug 2 14:31:34 UTC 2015

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.


Posted at Nginx Forum:,260692,260704#msg-260704

More information about the nginx mailing list