my module is such:
The pool is created with ngx_create_pool in module_init_process; I get momery
from the pool in the start of each request, and then use ngx_reset_pool in the
end of each request.
The ngx_reset_pool take pool->large each alloc pointer return to pool, and
each alloc pointer
Hello!
On Tue, Sep 27, 2022 at 04:05:54PM +0400, Sergey Kandaurov wrote:
> > On 27 Sep 2022, at 14:11, João Sousa Andrade
> > wrote:
> >
> > Thank you for the clarification Sergey.
> >
> > We have been running http3 in production for the past couple of weeks.
> > There's something we have n
Hello!
On Tue, Sep 27, 2022 at 03:25:18PM +0800, zjd wrote:
> # HG changeset patch
> # User Zhang Jinde
> # Date 1664261587 -28800
> # Tue Sep 27 14:53:07 2022 +0800
> # Node ID 226a75a3703db612ed13d4357ac1b71faef6974a
> # Parent ba5cf8f73a2d0a3615565bf9545f3d65216a0530
> Core: fix ngx_res
> On 27 Sep 2022, at 14:11, João Sousa Andrade wrote:
>
> Thank you for the clarification Sergey.
>
> We have been running http3 in production for the past couple of weeks.
> There's something we have noticed which I'm not entirely sure as to what is
> causing it.
>
> We have been getting l
Thank you for the clarification Sergey.
We have been running http3 in production for the past couple of weeks. There's
something we have noticed which I'm not entirely sure as to what is causing it.
We have been getting lots of errors of the form: "[error] 34#34: *338736 quic
no available clie
# HG changeset patch
# User Zhang Jinde
# Date 1664261587 -28800
# Tue Sep 27 14:53:07 2022 +0800
# Node ID 226a75a3703db612ed13d4357ac1b71faef6974a
# Parent ba5cf8f73a2d0a3615565bf9545f3d65216a0530
Core: fix ngx_reset_pool wild pointer's coredump
When frequently use ngx_reset_pool
