generic-library/webrtc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
ce8e077cf0
webrtc/tools/lsan/suppressions.txt

52 lines
2.0 KiB
Plaintext
Raw Normal View History

Add suppressions file for Leak Sanitizer. Add a suppressions file that must exist in order for the Leak Sanitizer (LSan) bot to be able to run with the default configuration. This bot is located in the new WebRTC FYI waterfall at: http://build.chromium.org/p/client.webrtc.fyi/waterfall More info about LSan on http://www.chromium.org/developers/testing/leaksanitizer BUG=none TEST=Running a local master+slave passes fine with this file added locally. R=niklas.enbom@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2135004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4636 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-08-28 22:29:35 +02:00
# This is a suppressions file that must exist in order for the Leak Sanitizer
# (LSan) bot to be able to run with the default configuration.
# More info about LSan on
# http://www.chromium.org/developers/testing/leaksanitizer
More libjingle LSan suppressions. The suppressions in r4988 were not enough to green up the LSan+ASan bot. Here's another round of suppressions to get the bot green which I have tested multiple runs without any leaks reported. BUG=2527,2528 TEST= GYP_DEFINES='asan=1 lsan=1 linux_use_tcmalloc=0 release_extra_cflags="-gline-tables-only"' gclient runhooks ninja -C out/Release libjingle_unittest export ASAN_SYMBOLIZER_PATH=`(pwd)`/third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer export ASAN_OPTIONS="detect_leaks=1 strict_memcmp=0" export LSAN_OPTIONS="suppressions=tools/lsan/suppressions.txt" out/Release/libjingle_peerconnection_unittest out/Release/libjingle_unittest TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2422004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4990 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 19:15:24 +02:00
#### Third-party leaks ####
# Leak reported in libstdc++
leak:std::string::_Rep::_S_create
#### Actual bugs in WebRTC code ####
Suppressions and PRESUBMIT.py for LSan The Leak Sanitizer will replace Valgrind memcheck when it's related tool Memory Sanitizer is ready. We should get our tests in shape so we can detect new leaks, which is why I'm adding these suppressions. More info at http://www.chromium.org/developers/testing/leaksanitizer Buildbot at http://build.chromium.org/p/client.webrtc.fyi/waterfall BUG=2515,2527,2528 TEST=Ran tests with the parameters described in webrtc:2527. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2421004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4988 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 16:16:17 +02:00
# libjingle_peerconnection_unittest
# https://code.google.com/p/webrtc/issues/detail?id=2528
Final round of LSan suppressions (take 2) Turns out I was running libjingle_unittest instead of libjingle_peerconnection_unittest on the bot machine when I was verifying the suppressions added in r4991 on the bot. This will hopefully be the last round. BUG=2528 TEST=running libjingle_unittest with these suppressions applied locally on the bot. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2426004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4993 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 21:26:27 +02:00
leak:cricket::FakeVideoMediaChannel::~FakeVideoMediaChannel
LSan suppressions for libjingle_peerconnection_unittest Some more leaks have entered the code a while ago so I'm suppressing them to green up the bot again. BUG=2528 TEST=Successful execution of the test using the steps described in webrtc:2528. TBR=wu@webrtc.org Review URL: https://webrtc-codereview.appspot.com/4419004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@5177 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-11-26 10:37:12 +01:00
leak:cricket::MediaSessionDescriptionFactory::CreateAnswer
leak:cricket::MediaSessionDescriptionFactory::CreateOffer
Final round of LSan suppressions (take 2) Turns out I was running libjingle_unittest instead of libjingle_peerconnection_unittest on the bot machine when I was verifying the suppressions added in r4991 on the bot. This will hopefully be the last round. BUG=2528 TEST=running libjingle_unittest with these suppressions applied locally on the bot. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2426004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4993 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 21:26:27 +02:00
leak:testing::internal::CmpHelperEQ
Final round of LSan suppressions. Since we don't have a trybot for LSan, this is the only way to resolve errors only happening on the bots (except running at the bot themselves). I suspect some errors only occurs on the bots since the compiler version differs (4.6 on bots, 4.6.3 on my machine). This last suppressions round was tested on an actual Chrome infra VM as well, with no errors. BUG=2528 TEST=ran successfully on the bot. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2424004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4991 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 20:13:28 +02:00
leak:webrtc::AudioDeviceLinuxALSA::InitMicrophone
More libjingle LSan suppressions. The suppressions in r4988 were not enough to green up the LSan+ASan bot. Here's another round of suppressions to get the bot green which I have tested multiple runs without any leaks reported. BUG=2527,2528 TEST= GYP_DEFINES='asan=1 lsan=1 linux_use_tcmalloc=0 release_extra_cflags="-gline-tables-only"' gclient runhooks ninja -C out/Release libjingle_unittest export ASAN_SYMBOLIZER_PATH=`(pwd)`/third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer export ASAN_OPTIONS="detect_leaks=1 strict_memcmp=0" export LSAN_OPTIONS="suppressions=tools/lsan/suppressions.txt" out/Release/libjingle_peerconnection_unittest out/Release/libjingle_unittest TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2422004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4990 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 19:15:24 +02:00
leak:webrtc::AudioDeviceLinuxALSA::InitSpeaker
LSan suppressions for libjingle_peerconnection_unittest Some more leaks have entered the code a while ago so I'm suppressing them to green up the bot again. BUG=2528 TEST=Successful execution of the test using the steps described in webrtc:2528. TBR=wu@webrtc.org Review URL: https://webrtc-codereview.appspot.com/4419004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@5177 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-11-26 10:37:12 +01:00
leak:webrtc::CreateIceCandidate
Final round of LSan suppressions. Since we don't have a trybot for LSan, this is the only way to resolve errors only happening on the bots (except running at the bot themselves). I suspect some errors only occurs on the bots since the compiler version differs (4.6 on bots, 4.6.3 on my machine). This last suppressions round was tested on an actual Chrome infra VM as well, with no errors. BUG=2528 TEST=ran successfully on the bot. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2424004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4991 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 20:13:28 +02:00
leak:webrtc::FakeConstraints::AddOptional
Suppressions and PRESUBMIT.py for LSan The Leak Sanitizer will replace Valgrind memcheck when it's related tool Memory Sanitizer is ready. We should get our tests in shape so we can detect new leaks, which is why I'm adding these suppressions. More info at http://www.chromium.org/developers/testing/leaksanitizer Buildbot at http://build.chromium.org/p/client.webrtc.fyi/waterfall BUG=2515,2527,2528 TEST=Ran tests with the parameters described in webrtc:2527. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2421004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4988 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 16:16:17 +02:00
leak:webrtc::WebRtcIdentityRequestObserver::OnSuccess
LSan suppressions for libjingle_peerconnection_unittest Some more leaks have entered the code a while ago so I'm suppressing them to green up the bot again. BUG=2528 TEST=Successful execution of the test using the steps described in webrtc:2528. TBR=wu@webrtc.org Review URL: https://webrtc-codereview.appspot.com/4419004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@5177 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-11-26 10:37:12 +01:00
leak:webrtc::WebRtcSessionDescriptionFactory::InternalCreateAnswer
leak:webrtc::WebRtcSessionDescriptionFactory::InternalCreateOffer
Final round of LSan suppressions. Since we don't have a trybot for LSan, this is the only way to resolve errors only happening on the bots (except running at the bot themselves). I suspect some errors only occurs on the bots since the compiler version differs (4.6 on bots, 4.6.3 on my machine). This last suppressions round was tested on an actual Chrome infra VM as well, with no errors. BUG=2528 TEST=ran successfully on the bot. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2424004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4991 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 20:13:28 +02:00
leak:WebRtcSdpTest::TestDeserializeRtcpFb
Final round of LSan suppressions (take 2) Turns out I was running libjingle_unittest instead of libjingle_peerconnection_unittest on the bot machine when I was verifying the suppressions added in r4991 on the bot. This will hopefully be the last round. BUG=2528 TEST=running libjingle_unittest with these suppressions applied locally on the bot. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2426004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4993 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 21:26:27 +02:00
leak:WebRtcSessionTest_TestAVOfferWithAudioOnlyAnswer_Test::TestBody
Suppressions and PRESUBMIT.py for LSan The Leak Sanitizer will replace Valgrind memcheck when it's related tool Memory Sanitizer is ready. We should get our tests in shape so we can detect new leaks, which is why I'm adding these suppressions. More info at http://www.chromium.org/developers/testing/leaksanitizer Buildbot at http://build.chromium.org/p/client.webrtc.fyi/waterfall BUG=2515,2527,2528 TEST=Ran tests with the parameters described in webrtc:2527. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2421004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4988 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 16:16:17 +02:00
# libjingle_unittest
# https://code.google.com/p/webrtc/issues/detail?id=2527
More libjingle LSan suppressions. The suppressions in r4988 were not enough to green up the LSan+ASan bot. Here's another round of suppressions to get the bot green which I have tested multiple runs without any leaks reported. BUG=2527,2528 TEST= GYP_DEFINES='asan=1 lsan=1 linux_use_tcmalloc=0 release_extra_cflags="-gline-tables-only"' gclient runhooks ninja -C out/Release libjingle_unittest export ASAN_SYMBOLIZER_PATH=`(pwd)`/third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer export ASAN_OPTIONS="detect_leaks=1 strict_memcmp=0" export LSAN_OPTIONS="suppressions=tools/lsan/suppressions.txt" out/Release/libjingle_peerconnection_unittest out/Release/libjingle_unittest TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2422004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4990 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 19:15:24 +02:00
leak:buzz::FakeXmppClient::SendStanza
Suppressions and PRESUBMIT.py for LSan The Leak Sanitizer will replace Valgrind memcheck when it's related tool Memory Sanitizer is ready. We should get our tests in shape so we can detect new leaks, which is why I'm adding these suppressions. More info at http://www.chromium.org/developers/testing/leaksanitizer Buildbot at http://build.chromium.org/p/client.webrtc.fyi/waterfall BUG=2515,2527,2528 TEST=Ran tests with the parameters described in webrtc:2527. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2421004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4988 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 16:16:17 +02:00
leak:buzz::XmppTask::XmppTask
More libjingle LSan suppressions. The suppressions in r4988 were not enough to green up the LSan+ASan bot. Here's another round of suppressions to get the bot green which I have tested multiple runs without any leaks reported. BUG=2527,2528 TEST= GYP_DEFINES='asan=1 lsan=1 linux_use_tcmalloc=0 release_extra_cflags="-gline-tables-only"' gclient runhooks ninja -C out/Release libjingle_unittest export ASAN_SYMBOLIZER_PATH=`(pwd)`/third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer export ASAN_OPTIONS="detect_leaks=1 strict_memcmp=0" export LSAN_OPTIONS="suppressions=tools/lsan/suppressions.txt" out/Release/libjingle_peerconnection_unittest out/Release/libjingle_unittest TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2422004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4990 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 19:15:24 +02:00
leak:HangoutPubSubClientTest::HangoutPubSubClientTest
leak:MucRoomConfigTaskTest::SetUp
leak:MucRoomDiscoveryTaskTest::SetUp
leak:MucRoomLookupTaskTest::SetUp
Suppressions and PRESUBMIT.py for LSan The Leak Sanitizer will replace Valgrind memcheck when it's related tool Memory Sanitizer is ready. We should get our tests in shape so we can detect new leaks, which is why I'm adding these suppressions. More info at http://www.chromium.org/developers/testing/leaksanitizer Buildbot at http://build.chromium.org/p/client.webrtc.fyi/waterfall BUG=2515,2527,2528 TEST=Ran tests with the parameters described in webrtc:2527. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2421004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4988 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 16:16:17 +02:00
leak:MucRoomUniqueHangoutIdTaskTest::SetUp
More libjingle LSan suppressions. The suppressions in r4988 were not enough to green up the LSan+ASan bot. Here's another round of suppressions to get the bot green which I have tested multiple runs without any leaks reported. BUG=2527,2528 TEST= GYP_DEFINES='asan=1 lsan=1 linux_use_tcmalloc=0 release_extra_cflags="-gline-tables-only"' gclient runhooks ninja -C out/Release libjingle_unittest export ASAN_SYMBOLIZER_PATH=`(pwd)`/third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer export ASAN_OPTIONS="detect_leaks=1 strict_memcmp=0" export LSAN_OPTIONS="suppressions=tools/lsan/suppressions.txt" out/Release/libjingle_peerconnection_unittest out/Release/libjingle_unittest TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2422004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4990 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 19:15:24 +02:00
leak:PingTaskTest::SetUp
Suppressions and PRESUBMIT.py for LSan The Leak Sanitizer will replace Valgrind memcheck when it's related tool Memory Sanitizer is ready. We should get our tests in shape so we can detect new leaks, which is why I'm adding these suppressions. More info at http://www.chromium.org/developers/testing/leaksanitizer Buildbot at http://build.chromium.org/p/client.webrtc.fyi/waterfall BUG=2515,2527,2528 TEST=Ran tests with the parameters described in webrtc:2527. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2421004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4988 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 16:16:17 +02:00
leak:PingXmppClient::SendStanza
leak:PubSubClientTest::PubSubClientTest
More libjingle LSan suppressions. The suppressions in r4988 were not enough to green up the LSan+ASan bot. Here's another round of suppressions to get the bot green which I have tested multiple runs without any leaks reported. BUG=2527,2528 TEST= GYP_DEFINES='asan=1 lsan=1 linux_use_tcmalloc=0 release_extra_cflags="-gline-tables-only"' gclient runhooks ninja -C out/Release libjingle_unittest export ASAN_SYMBOLIZER_PATH=`(pwd)`/third_party/llvm-build/Release+Asserts/bin/llvm-symbolizer export ASAN_OPTIONS="detect_leaks=1 strict_memcmp=0" export LSAN_OPTIONS="suppressions=tools/lsan/suppressions.txt" out/Release/libjingle_peerconnection_unittest out/Release/libjingle_unittest TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2422004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4990 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 19:15:24 +02:00
leak:PubSubTasksTest::PubSubTasksTest
leak:talk_base::HttpData::changeHeader
leak:talk_base::HttpParser::ProcessLine
leak:talk_base::HttpServer::Connection::BeginProcess
leak:talk_base::IdTimeoutTask::IdTimeoutTask
leak:talk_base::OpenSSLCertificate::FromPEMString
leak:talk_base::OpenSSLIdentity::FromPEMStrings
leak:talk_base::TaskParent::TaskParent
leak:talk_base::unstarted_task_test_DoNotDeleteTask2_Test::TestBody
Suppressions and PRESUBMIT.py for LSan The Leak Sanitizer will replace Valgrind memcheck when it's related tool Memory Sanitizer is ready. We should get our tests in shape so we can detect new leaks, which is why I'm adding these suppressions. More info at http://www.chromium.org/developers/testing/leaksanitizer Buildbot at http://build.chromium.org/p/client.webrtc.fyi/waterfall BUG=2515,2527,2528 TEST=Ran tests with the parameters described in webrtc:2527. TBR=phoglund@webrtc.org Review URL: https://webrtc-codereview.appspot.com/2421004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@4988 4adac7df-926f-26a2-2b94-8c16560cd09d
2013-10-17 16:16:17 +02:00
Reference in New Issue Copy Permalink