diff options
author | earthdok@google.com <earthdok@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-07 22:09:32 +0000 |
---|---|---|
committer | earthdok@google.com <earthdok@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-07 22:09:32 +0000 |
commit | b2206da557c9bb6e7758e02fe74153eacab5c677 (patch) | |
tree | c94110eba888c7364ebc4c703b3eef4c2b47f4c4 /tools | |
parent | 815deba9740c65b762544990af363817b0881268 (diff) | |
download | chromium_src-b2206da557c9bb6e7758e02fe74153eacab5c677.zip chromium_src-b2206da557c9bb6e7758e02fe74153eacab5c677.tar.gz chromium_src-b2206da557c9bb6e7758e02fe74153eacab5c677.tar.bz2 |
Annotate LeakyLazyInstance as a leak. Remove HeapChecker suppressions.
The two suppressions removed by this CL have not fired for a long time,
for some unknown reason. It's still a good idea to annotate all
intentional leaks though.
BUG=83345
R=jar@chromium.org,darin@chromium.org
CC=glider@chromium.org
Review URL: https://chromiumcodereview.appspot.com/16440006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@204953 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools')
-rw-r--r-- | tools/heapcheck/suppressions.txt | 16 |
1 files changed, 0 insertions, 16 deletions
diff --git a/tools/heapcheck/suppressions.txt b/tools/heapcheck/suppressions.txt index 5868c6f..5bbef01 100644 --- a/tools/heapcheck/suppressions.txt +++ b/tools/heapcheck/suppressions.txt @@ -295,13 +295,6 @@ fun:content::BrowserThreadTest_NotReleasedIfTargetThreadNonExistent_Test::TestBody } { - Intentional LeakyLazyInstanceTraits leaks - Heapcheck:Leak - ... - fun:base::internal::LeakyLazyInstanceTraits::New - fun:base::LazyInstance::Pointer -} -{ Intentional leak in object tracking statics to avoid shutdown race Heapcheck:Leak ... @@ -319,15 +312,6 @@ fun:tracked_objects::ThreadData::TallyA* } { - NSS is initialized (LeakyLazyInstance) but intentionally never shut down - Heapcheck:Leak - ... - fun:InitSessionCacheLocks - fun:initSessionCacheLocksLazily - ... - fun:ssl_InitSessionCacheLocks -} -{ FileStream::Context can leak through WorkerPool by design (Linux) Heapcheck:Leak fun:net::FileStream::FileStream |