Re: [grpc-io] grpc 1.11, pure virtual call failure for cq->Next.

[Nicolas Noble]

99% of the time, a pure virtual method call exception is caused by a use-after-free, either in our code or yours.

This being said, this version is fairly old, and it might be worth upgrading to see if there's any difference.

On Thu, Dec 13, 2018 at 7:16 AM solomon lifshits <solom...@gmail.com> wrote:

Hello.

We use bidirectional streaming in our grpc app. In our system testing, we occasionally( once a day at average) face 'pure virtual call' exception when calling Next method on completion queue. The server serves about 30 clients(that is 30 bidirectional streams) in parallel at any given moment, when communication is read-heavy on server side(much fewer writes than reads). No concurrent calls on the same stream. No shared server contexts across different rpc calls. Server calls Finish on each stream after a read failure, and destroys the stream object when the finish tag is delivered on completion queue. AsyncNotifyDone api is not used. Version : grpc-1.11. Any thoughts on such a failure? 

Thanks! 

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+u...@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/ca819ce0-809a-4081-9ef6-afe03cc11645%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.