-
-
Notifications
You must be signed in to change notification settings - Fork 380
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Is this sanitizer deadlock report a false positive? #1293
Comments
The stacks are completely unclear but I guess this is about |
The PR seems to make a difference, in that the thread sanitizer complains about the same issue somewhere else
|
This is about the state callback of one of the transports, but the stack are truncated so I don't know which one. It could be the same kind of false positive. |
There have been some sanitizer reports that were stated to be likely false positives (data race and double lock of mutex). I have another TSAN report here about a potential deadlock and I am wondering if I can just suppress it.
The report comes after suppressing
mutex
andrace
issues in libdatachannel in the suppressions fileanything to worry about here? I should note that the double mutex lock and data race reports also seemed to relate to
WebSocket
and/orconnect()
calls.The text was updated successfully, but these errors were encountered: