Hi,
did you got the answer for the below??
Just a quick question, when is destroy_channel(...) called? We are using
the same channel over and over. Does that mean destroy_channel is not
called?
On Friday, September 30, 2016 at 5:51:30 AM UTC+5:30, douy...@gmail.com
wrote:
>
> Thanks for the
Thanks for the reply. I will try GRPC_STREAM_REFCOUNT_DEBUG.
Just a quick question, when is destroy_channel(...) called? We are using
the same channel over and over. Does that mean destroy_channel is not
called?
On Thursday, September 29, 2016 at 3:22:44 PM UTC-7, Yang Gao wrote:
>
> Hi, The stu
Hi, The stub can be shared by different calls, but the memory is freed in
https://github.com/grpc/grpc/blob/master/src/core/lib/surface/channel.c#L311
You can try to define GRPC_STREAM_REFCOUNT_DEBUG to have more logs.
On Tue, Sep 27, 2016 at 5:17 PM, wrote:
> I am tracking down a memory leak,
I am tracking down a memory leak, and it leads to the NewStub call (async
in my case). In our code, for every rpc request from the client, a NewStub
is created to send the request. The stub object returned from NewStub is
correctly deleted (as a unique_ptr), but something else during the call i
