Re: I think I found a fix for the memory leak issue on gRPC module

2024-05-27 Thread Sergey Kandaurov
On Mon, May 27, 2024 at 02:06:58PM +0400, Roman Arutyunyan wrote: > Hi, > # HG changeset patch > # User Roman Arutyunyan > # Date 1716477338 -14400 > # Thu May 23 19:15:38 2024 +0400 > # Node ID f7d53c7f70140b1cd1eaf51ce4346a873692f879 > # Parent f58b6f6362387eeace46043a6fc0bceb56a6786a >

Re: I think I found a fix for the memory leak issue on gRPC module

2024-05-27 Thread Sergey Kandaurov
; > > From: nginx-devel On Behalf Of Sangmin Lee > > Sent: Thursday, April 4, 2024 19:29 > > To: nginx-devel@nginx.org > > Subject: I think I found a fix for the memory leak issue on gRPC module > > > > CAUTION: This email has been sent from an external sourc

Re: I think I found a fix for the memory leak issue on gRPC module

2024-05-27 Thread Roman Arutyunyan
unbound > > > accumulation of ngx_chain_t objects (although, at very slow rate). Gzip > > > module had a similar issue (https://trac.nginx.org/nginx/ticket/1046). > > > Attaching somewhat simplified patch based on yours. I was able to > > > reproduce the

Re: I think I found a fix for the memory leak issue on gRPC module

2024-05-23 Thread Roman Arutyunyan
/ticket/1046). > > Attaching somewhat simplified patch based on yours. I was able to reproduce > > the issue locally and the patch fixes it. > > > > From: nginx-devel On Behalf Of Sangmin Lee > > Sent: Thursday, April 4, 2024 19:29 > > To: nginx-devel@ngi

Re: I think I found a fix for the memory leak issue on gRPC module

2024-05-22 Thread Roman Arutyunyan
pril 4, 2024 19:29 > To: nginx-devel@nginx.org > Subject: I think I found a fix for the memory leak issue on gRPC module > > CAUTION: This email has been sent from an external source. Do not click > links, open attachments, or provide sensitive business information unless you &g