<blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
> I am a new pie to everything here, so please just ignore anything what i've<br>
> done improperly.<br>
><br>
> Serveral days ago, when I was debugging my module, I crash the nginx process<br>
> by change. I am playing with source code 0.8.36. then I tried the same thing<br>
> under 0.8.44, crash happened again.<br>
><br>
> nginx.conf:<br>
><br>
> daemon off;<br>
> master_process off;<br>
><br>
> I started nginx in my terminal, and issued the configuration reloading<br>
> command twice in another terminal. About 30 seconds later, the process just<br>
> end up with "Segmentation fault".<br>
><br>
> I digged the code, found what caused this problem was:<br>
><br>
> in ngx_clean_old_cycles, the ngx_cycle_t::connections in the second old<br>
> cycle in ngx_old_cycles was not initialized properly, which should be done<br>
> in ngx_event_process_init, which was only called once in<br>
> ngx_single_process_cycle. So, the following __cycle__s created after<br>
> reconfiguring was not initialized by ngx_event_process_init.<br>
><br>
> I don't know if I describe the "problem" right, or this behavior should be<br>
> considered as a BUG.<br>
<br>
"master_process off" mode is intended only for development and reloading<br>
may not work reliably in this mode. If you to test reloading, you should<br>
run "master_process on".<br>
<br>
<br>
</blockquote></div>Thanks for you quick replying.. </blockquote><div></div><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">But, with all due respect, the question is, what we need this mode for, if some feature may break during the custom module development.<br>
</blockquote><div> </div>