Re: [grpc-io] Re: memory leak in grpc

2022-05-27 Thread Vishal Kaushik
Hello, After I started my QT application using Valgring, it became unresponsive and I had to kill it. Server was running fine and no issues were reported from there. Best Regards *Vishal Kaushik* Anzo Controls Private Limited 6th Floor Avanta, BPTP Park Centra Sector 30, Gurugram, 122003 Con

Re: [grpc-io] Re: memory leak in grpc

2022-05-26 Thread 'Esun Kim' via grpc.io
>From the output of Valgrind, if Finish call was called properly against ClientAsyncResponseReader, I suspect that server is killed while serving the client, resulting in active call objects leaked. On Thu, May 26, 2022 at 3:16 AM Vishal Kaushik < vishal.kaus...@anzocontrols.com> wrote: > Thanks

Re: [grpc-io] Re: memory leak in grpc

2022-05-26 Thread Vishal Kaushik
Thanks for your email. As I am using gRPC to connect to a machine and run it, you will not be able to replicate it. But you can do teamviewer with me for a few mins and I think you can understand the problem easily. I ran the Valgard and it gave me so many lines of messages. Few of them are below:

[grpc-io] Re: memory leak in grpc

2022-05-25 Thread 'veb...@google.com' via grpc.io
I see a couple of new operation without free in your code. So you may want to clean your code first and use MSAN or Valgrind to track down which objects are not freed. If you think that gRPC has its own memory leak, please give us a small repro we can run so that we can investigate it further.