Hi, Lord,
Thank you!

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

But the issue in my case is not related to nginx's pool mechanism.
It is caused by some build-in modules which won't release it allocated memory at all. e.g.
ngx_event_core_module.init_process does some allocating but there 's no ngx_event_core_module.exit_process at all, so the memory it allocated will only be released by operation system process manager only when the worker process exits. it is plain that this will be reported as memory leak by valgrind.

Just as Maxim said, I plan to write a new process_cycle for my shared library and record all unreleased memory and do release them at the end of process_cycle.


Regards.
Xfeep