Hi Team,
I am using centos based opensource nginx for our work. During testing we could see huge spike in memory consumption because of memory leaks happening.
Integrated valgrind .to nginx. Below are few leak information which shows. I am trying to debug these. if anyone fixed these issues or we have work around please let me know
==29923== 4,280 bytes in 1 blocks are possibly lost in loss record 13 of 20
==29923== at 0x4C29BC3: malloc (vg_replace_malloc.c:299)
==29923== by 0x4734EF: ngx_alloc (ngx_alloc.c:22)
==29923== by 0x450F41: ngx_palloc_large (ngx_palloc.c:220)
==29923== by 0x45128B: ngx_palloc (ngx_palloc.c:131)
==29923== by 0x4513DD: ngx_pcalloc (ngx_palloc.c:302)
==29923== by 0x45256B: ngx_hash_keys_array_init (ngx_hash.c:702)
==29923== by 0x49AC05: ngx_http_variables_add_core_vars (ngx_http_variables.c:2583)
==29923== by 0x488D69: ngx_http_core_preconfiguration (ngx_http_core_module.c:3187)
==29923== by 0x4835AF: ngx_http_block (ngx_http.c:227)
==29923== by 0x463A68: ngx_conf_handler (ngx_conf_file.c:463)
==29923== by 0x463A68: ngx_conf_parse (ngx_conf_file.c:319)
==29923== by 0x461107: ngx_init_cycle (ngx_cycle.c:275)
==29923== by 0x44F7B3: main (nginx.c:292)
==29923== 6,272 bytes in 1 blocks are possibly lost in loss record 14 of 20
==29923== at 0x4C29BC3: malloc (vg_replace_malloc.c:299)
==29923== by 0x4734EF: ngx_alloc (ngx_alloc.c:22)
==29923== by 0x450F41: ngx_palloc_large (ngx_palloc.c:220)
==29923== by 0x45128B: ngx_palloc (ngx_palloc.c:131)
==29923== by 0x451E5F: ngx_hash_init (ngx_hash.c:378)
==29923== by 0x49AFBE: ngx_http_variables_init_vars (ngx_http_variables.c:2705)
==29923== by 0x483C51: ngx_http_block (ngx_http.c:314)
==29923== by 0x463A68: ngx_conf_handler (ngx_conf_file.c:463)
==29923== by 0x463A68: ngx_conf_parse (ngx_conf_file.c:319)
==29923== by 0x461107: ngx_init_cycle (ngx_cycle.c:275)
==29923== by 0x44F7B3: main (nginx.c:292)
==29923== 16,384 bytes in 1 blocks are possibly lost in loss record 16 of 20
==29923== at 0x4C2BC3C: memalign (vg_replace_malloc.c:857)
==29923== by 0x4C2BD01: posix_memalign (vg_replace_malloc.c:1020)
==29923== by 0x4735A0: ngx_memalign (ngx_alloc.c:57)
==29923== by 0x450EC1: ngx_palloc_block (ngx_palloc.c:186)
==29923== by 0x451284: ngx_palloc_small (ngx_palloc.c:173)
==29923== by 0x451284: ngx_palloc (ngx_palloc.c:127)
==29923== by 0x452788: ngx_array_init (ngx_array.h:44)
==29923== by 0x452788: ngx_hash_add_key (ngx_hash.c:804)
==29923== by 0x4D915B: ngx_stream_add_variable (ngx_stream_variables.c:190)
==29923== by 0x4D9C0D: ngx_stream_variables_add_core_vars (ngx_stream_variables.c:1133)
==29923== by 0x4DC660: ngx_stream_core_preconfiguration (ngx_stream_core_module.c:344)
==29923== by 0x4D7B21: ngx_stream_block (ngx_stream.c:164)
==29923== by 0x463A68: ngx_conf_handler (ngx_conf_file.c:463)
==29923== by 0x463A68: ngx_conf_parse (ngx_conf_file.c:319)
==29923== by 0x461107: ngx_init_cycle (ngx_cycle.c:275)
Thanks,
Sushma
I am using centos based opensource nginx for our work. During testing we could see huge spike in memory consumption because of memory leaks happening.
Integrated valgrind .to nginx. Below are few leak information which shows. I am trying to debug these. if anyone fixed these issues or we have work around please let me know
==29923== 4,280 bytes in 1 blocks are possibly lost in loss record 13 of 20
==29923== at 0x4C29BC3: malloc (vg_replace_malloc.c:299)
==29923== by 0x4734EF: ngx_alloc (ngx_alloc.c:22)
==29923== by 0x450F41: ngx_palloc_large (ngx_palloc.c:220)
==29923== by 0x45128B: ngx_palloc (ngx_palloc.c:131)
==29923== by 0x4513DD: ngx_pcalloc (ngx_palloc.c:302)
==29923== by 0x45256B: ngx_hash_keys_array_init (ngx_hash.c:702)
==29923== by 0x49AC05: ngx_http_variables_add_core_vars (ngx_http_variables.c:2583)
==29923== by 0x488D69: ngx_http_core_preconfiguration (ngx_http_core_module.c:3187)
==29923== by 0x4835AF: ngx_http_block (ngx_http.c:227)
==29923== by 0x463A68: ngx_conf_handler (ngx_conf_file.c:463)
==29923== by 0x463A68: ngx_conf_parse (ngx_conf_file.c:319)
==29923== by 0x461107: ngx_init_cycle (ngx_cycle.c:275)
==29923== by 0x44F7B3: main (nginx.c:292)
==29923== 6,272 bytes in 1 blocks are possibly lost in loss record 14 of 20
==29923== at 0x4C29BC3: malloc (vg_replace_malloc.c:299)
==29923== by 0x4734EF: ngx_alloc (ngx_alloc.c:22)
==29923== by 0x450F41: ngx_palloc_large (ngx_palloc.c:220)
==29923== by 0x45128B: ngx_palloc (ngx_palloc.c:131)
==29923== by 0x451E5F: ngx_hash_init (ngx_hash.c:378)
==29923== by 0x49AFBE: ngx_http_variables_init_vars (ngx_http_variables.c:2705)
==29923== by 0x483C51: ngx_http_block (ngx_http.c:314)
==29923== by 0x463A68: ngx_conf_handler (ngx_conf_file.c:463)
==29923== by 0x463A68: ngx_conf_parse (ngx_conf_file.c:319)
==29923== by 0x461107: ngx_init_cycle (ngx_cycle.c:275)
==29923== by 0x44F7B3: main (nginx.c:292)
==29923== 16,384 bytes in 1 blocks are possibly lost in loss record 16 of 20
==29923== at 0x4C2BC3C: memalign (vg_replace_malloc.c:857)
==29923== by 0x4C2BD01: posix_memalign (vg_replace_malloc.c:1020)
==29923== by 0x4735A0: ngx_memalign (ngx_alloc.c:57)
==29923== by 0x450EC1: ngx_palloc_block (ngx_palloc.c:186)
==29923== by 0x451284: ngx_palloc_small (ngx_palloc.c:173)
==29923== by 0x451284: ngx_palloc (ngx_palloc.c:127)
==29923== by 0x452788: ngx_array_init (ngx_array.h:44)
==29923== by 0x452788: ngx_hash_add_key (ngx_hash.c:804)
==29923== by 0x4D915B: ngx_stream_add_variable (ngx_stream_variables.c:190)
==29923== by 0x4D9C0D: ngx_stream_variables_add_core_vars (ngx_stream_variables.c:1133)
==29923== by 0x4DC660: ngx_stream_core_preconfiguration (ngx_stream_core_module.c:344)
==29923== by 0x4D7B21: ngx_stream_block (ngx_stream.c:164)
==29923== by 0x463A68: ngx_conf_handler (ngx_conf_file.c:463)
==29923== by 0x463A68: ngx_conf_parse (ngx_conf_file.c:319)
==29923== by 0x461107: ngx_init_cycle (ngx_cycle.c:275)
Thanks,
Sushma