SIGABRT:Check (v & (kMuWriter | kMuReader)) != (kMuWriter | kMuReader) failed: %s: Mutex corrupt: both reader and writer lock held: %p #1776
Unanswered
JiachengLiang
asked this question in
Q&A
Replies: 1 comment
-
version information: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I started a thread. The main body of the thread uses the google::protobuf::DescriptorPool::FindMessageTypeByName interface of google-protobuf.
Once the thread is running, it will continue to restart.
I found the following exception stack through gdb, and printed the relevant parameter information of the function on the top of the stack.
Could you please tell me about the error reported by abseil-cpp "Check (v & (kMuWriter | kMuReader)) != (kMuWriter | kMuReader) failed: %s: Mutex corrupt: both reader and writer lock held: %p". What could be the cause?
In addition, this problem only occurs when google-protobuf and abseil-cpp and my business code all use asan. Once these three are not used asan, the thread will run normally and will not restart.
Beta Was this translation helpful? Give feedback.
All reactions