gRPC server crash when calling CompletionQueue::AsyncNext and then grpc_byte_buffer_destroy
205 views
Skip to first unread message
Nikita Tokariev
Oct 13, 2021, 7:11:34 AM10/13/21
to grpc.io
Hi, I am using gRPC version 1.35. I am experiencing the following crash and I believe the problem is on gRPC side. I've found the following page with similar crash https://github.com/grpc/grpc/issues/23270 . I would appreciate any suggestions from your side. Thank you! Please find the crash trace below.
#0 0x00007fd5afedb387 in raise () from /lib64/libc.so.6 #1 0x00007fd5afedca78 in abort () from /lib64/libc.so.6 #2 0x00007fd5aff1df67 in __libc_message () from /lib64/libc.so.6 #3 0x00007fd5aff26329 in _int_free () from /lib64/libc.so.6 #4 0x00007fd5b3b306ca in gpr_free () from /lib64/libgpr.so.14 #5 0x00007fd5b5aaabdc in grpc_byte_buffer_destroy () from /lib64/libgrpc.so.14 #6 0x00007fd5b601bc5c in grpc::CoreCodegen::grpc_byte_buffer_destroy(grpc_byte_buffer*) () from /lib64/libgrpc++.so.1 #7 0x00007fd5b7337e56 in grpc::ByteBuffer::Clear (this=0x7fd2cd76e490) at /usr/include/grpcpp/impl/codegen/byte_buffer.h:124 #8 grpc::internal::CallOpSendMessage::FinishOp (status=0x7fd5a603c88f, this=0x7fd2cd76e480) at /usr/include/grpcpp/impl/codegen/call_op_set.h:328 #9 grpc::internal::CallOpSet<grpc::internal::CallOpSendInitialMetadata, grpc::internal::CallOpSendMessage, grpc::internal::CallOpServerSendStatus, grpc::internal::CallNoOp<4>, grpc::internal::CallNoOp<5>, grpc::internal::CallNoOp<6> >::FinalizeResult (this=0x7fd2cd76e450, tag=0x7fd5a603c890, status=0x7fd5a603c88f) at /usr/include/grpcpp/impl/codegen/call_op_set.h:917 #10 0x00007fd5b601b703 in grpc::CompletionQueue::AsyncNextInternal(void**, bool*, gpr_timespec) () from /lib64/libgrpc++.so.1 #11 0x00007fd5b7330f32 in grpc::CompletionQueue::AsyncNext<std::chrono::time_point<std::chrono::_V2::system_clock, std::chrono::duration<long, std::ratio<1l, 1000000000l> > > > (deadline=..., ok=0x7fd5a603c88f, tag=0x7fd5a603c890, this=0x7fd2cd7596f0) at /usr/include/grpcpp/impl/codegen/time.h:81
#0 0x00007fd5afedb387 in raise () from /lib64/libc.so.6 #1 0x00007fd5afedca78 in abort () from /lib64/libc.so.6 #2 0x00007fd5aff1df67 in __libc_message () from /lib64/libc.so.6 #3 0x00007fd5aff26329 in _int_free () from /lib64/libc.so.6 #4 0x00007fd5b3b306ca in gpr_free () from /lib64/libgpr.so.14 #5 0x00007fd5b5aaabdc in grpc_byte_buffer_destroy () from /lib64/libgrpc.so.14 #6 0x00007fd5b601bc5c in grpc::CoreCodegen::grpc_byte_buffer_destroy(grpc_byte_buffer*) () from /lib64/libgrpc++.so.1 #7 0x00007fd5b7337e56 in grpc::ByteBuffer::Clear (this=0x7fd2cd76e490) at /usr/include/grpcpp/impl/codegen/byte_buffer.h:124 #8 grpc::internal::CallOpSendMessage::FinishOp (status=0x7fd5a603c88f, this=0x7fd2cd76e480) at /usr/include/grpcpp/impl/codegen/call_op_set.h:328 #9 grpc::internal::CallOpSet<grpc::internal::CallOpSendInitialMetadata, grpc::internal::CallOpSendMessage, grpc::internal::CallOpServerSendStatus, grpc::internal::CallNoOp<4>, grpc::internal::CallNoOp<5>, grpc::internal::CallNoOp<6> >::FinalizeResult (this=0x7fd2cd76e450, tag=0x7fd5a603c890, status=0x7fd5a603c88f) at /usr/include/grpcpp/impl/codegen/call_op_set.h:917 #10 0x00007fd5b601b703 in grpc::CompletionQueue::AsyncNextInternal(void**, bool*, gpr_timespec) () from /lib64/libgrpc++.so.1 #11 0x00007fd5b7330f32 in grpc::CompletionQueue::AsyncNext<std::chrono::time_point<std::chrono::_V2::system_clock, std::chrono::duration<long, std::ratio<1l, 1000000000l> > > > (deadline=..., ok=0x7fd5a603c88f, tag=0x7fd5a603c890, this=0x7fd2cd7596f0) at /usr/include/grpcpp/impl/codegen/time.h:81
AJ Heller
Oct 20, 2021, 2:08:09 PM10/20/21
to grpc.io
There have a handful of crash fixes since January, when 1.35 was released. Can you reproduce this with v1.41? If so, a minrepro would be helpful.
AJ Heller
Oct 20, 2021, 2:12:07 PM10/20/21
to grpc.io
*There have _been_ a handful ...
Reply all
Reply to author
Forward
0 new messages