Thanks Valentin, The issue fixedby Payne Chu - Nginx Mailing List - English
Finally I can reproduce even in the Homebrew version. It will only leak when I use relative path. and all version also can reproduce. b4 I test Homebrew version with full path not relative path that's the different....XD~ map $pid $public_root { default public; } <-- this one relative path leak happened map $pid $public_root { default /usr/local/Cellar/nginx/1.4.1/public; } <- this oby Payne Chu - Nginx Mailing List - English
https://groups.google.com/forum/#!topic/openresty-en/ArNhoL7Ol2U here is the reply from OpenResty's agentzh. seems the leak come from nginx 1.4.1's core. Maybe Homebrew have some patch fixed this issue ?by Payne Chu - Nginx Mailing List - English
here it is nginx version: ngx_openresty/1.4.1.1 TLS SNI support enabled configure arguments: --prefix=/usr/local/openresty/nginx --with-cc-opt='-I/usr/local/Cellar/pcre/8.33/include -I/usr/local/Cellar/luajit/2.02/luajit2.0/include' --add-module=../ngx_devel_kit-0.2.18 --add-module=../echo-nginx-module-0.45 --add-module=../xss-nginx-module-0.03rc9 --add-module=../ngx_coolkit-0.2rc1 --add-moduby Payne Chu - Nginx Mailing List - English
recently I try to use map directive to make my nginx.conf DRY. like below `map $pid $public_root { default public; }` and in one of server directive I put below `root $public_root;` I try to `ab` test with retrieve a static html. the nginx will eat all ram. if I reset back to `root public;` it will maintain the ram in low evel. so we should avoid to use map directive ? My Env: Mby Payne Chu - Nginx Mailing List - English