From d486dc1bd7f1e0eff7118f14b22768067dcd9cef Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Peter=20Bostr=C3=B6m?= Date: Tue, 26 Apr 2016 13:23:12 +0200 Subject: [PATCH] Remove some TSan deadlock suppressions. Looks like these are no longer actively triggering, so they can be removed. BUG=webrtc:2999 R=kjellander@webrtc.org Review URL: https://codereview.webrtc.org/1916923002 . Cr-Commit-Position: refs/heads/master@{#12502} --- webrtc/build/sanitizers/tsan_suppressions_webrtc.cc | 2 -- 1 file changed, 2 deletions(-) diff --git a/webrtc/build/sanitizers/tsan_suppressions_webrtc.cc b/webrtc/build/sanitizers/tsan_suppressions_webrtc.cc index 30a9a4572e..fc7ddbf23b 100644 --- a/webrtc/build/sanitizers/tsan_suppressions_webrtc.cc +++ b/webrtc/build/sanitizers/tsan_suppressions_webrtc.cc @@ -76,9 +76,7 @@ char kTSanDefaultSuppressions[] = // Potential deadlocks detected after roll in r6516. // https://code.google.com/p/webrtc/issues/detail?id=3509 -"deadlock:webrtc::RTCPReceiver::SetSsrcs\n" "deadlock:webrtc::test::UdpSocketManagerPosixImpl::RemoveSocket\n" -"deadlock:webrtc::vcm::VideoReceiver::RegisterPacketRequestCallback\n" // TODO(pbos): Trace events are racy due to lack of proper POD atomics. // https://code.google.com/p/webrtc/issues/detail?id=2497