I'm facing the same issue that was reported initially on this thread
Looking at the C++ client API and generated code, it seems that channels
are intended to be long-lived and shared (std::shared_ptr), while stub are
intended to be short lived (std::unique_ptr).
If I keep one long lived channel
Hi,
We will need some more details to understand what is going on. But I am not
aware of any leaking in stub and channel.
You can either provide some sort of repro or some debug information to show
that memory has been leaked.
Thanks.
On Tue, Jan 30, 2018 at 10:11 PM, wrote:
> I am facing this
I am facing this problem , can you give a help ? thanks
在 2016年9月28日星期三 UTC+8上午8:17:48，douy...@gmail.com写道：
>
> 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
I eventually by-pass the problem by reusing the same stub.
On Tuesday, September 12, 2017 at 7:21:30 PM UTC+8, Sandeep ananthula wrote:
>
> hi,
> am also facing the same issue, can you please help me if the issue is
> resolved for you.
>
> Thanks in Advance
>
>
> On Wednesday, September 28, 2016
hi,
am also facing the same issue, can you please help me if the issue is
resolved for you.
Thanks in Advance
On Wednesday, September 28, 2016 at 5:47:48 AM UTC+5:30, douy...@gmail.com
wrote:
>
> I am tracking down a memory leak, and it leads to the NewStub call (async
> in my case). In our
