August 02, 2015 10:31AM
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
Subject Author Posted

Memory leaks when used as a shared library

xfeep July 31, 2015 09:57PM

Re: Memory leaks when used as a shared library

xfeep July 31, 2015 10:32PM

Re: Memory leaks when used as a shared library

Maxim Dounin August 01, 2015 10:56PM

Re: Memory leaks when used as a shared library

xfeep August 02, 2015 10:31AM

Re: Memory leaks when used as a shared library

Lord Nynex August 04, 2015 03:36PM

Re: Memory leaks when used as a shared library

xfeep August 04, 2015 07:50PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 293
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready