summaryrefslogtreecommitdiffstats
path: root/tools/valgrind/drmemory/suppressions_full.txt
diff options
context:
space:
mode:
authorrnk@chromium.org <rnk@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-04-30 15:01:35 +0000
committerrnk@chromium.org <rnk@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-04-30 15:01:35 +0000
commit7ad8570b37d60783dfff03a82fbdf5f3f98f16ed (patch)
treed3e4c436a8f6f12991d7f26806ab0e6059499214 /tools/valgrind/drmemory/suppressions_full.txt
parent59dccdba6fbba3968c2f77a561e8c4888fa275f6 (diff)
downloadchromium_src-7ad8570b37d60783dfff03a82fbdf5f3f98f16ed.zip
chromium_src-7ad8570b37d60783dfff03a82fbdf5f3f98f16ed.tar.gz
chromium_src-7ad8570b37d60783dfff03a82fbdf5f3f98f16ed.tar.bz2
Widen DrMemory suppression for Windows TlsSetValue leaks.
Previously we were seeing this leak coming through system dlls, but now we see it through Chrome's ThreadLocalPlatform::SetValueInSlot. Perhaps this allocation occurs after crossing a threshold of calls, so the callstack is not really predictable as the number of callers changes. TBR=bruening@chromium.org BUG=DrMemory i#778 Review URL: https://chromiumcodereview.appspot.com/10273011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@134531 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/valgrind/drmemory/suppressions_full.txt')
-rw-r--r--tools/valgrind/drmemory/suppressions_full.txt8
1 files changed, 0 insertions, 8 deletions
diff --git a/tools/valgrind/drmemory/suppressions_full.txt b/tools/valgrind/drmemory/suppressions_full.txt
index a29a60d..689251c 100644
--- a/tools/valgrind/drmemory/suppressions_full.txt
+++ b/tools/valgrind/drmemory/suppressions_full.txt
@@ -858,8 +858,6 @@ USP10.dll!ScriptPositionSingleGlyph
LEAK
name=http://code.google.com/p/drmemory/issues/detail?id=778 a
KERNELBASE.dll!TlsSetValue
-RSAENH.dll!*
-RSAENH.dll!*
# Originally filed as: http://crbug.com/109281
LEAK
@@ -875,12 +873,6 @@ name=http://code.google.com/p/drmemory/issues/detail?id=778 c
*!_PR_AttachThread
*!_PRI_AttachThread
-LEAK
-name=http://code.google.com/p/drmemory/issues/detail?id=778 d
-KERNELBASE.dll!TlsSetValue
-MSWSOCK.dll!*
-KERNEL32.dll!BaseThreadInitThunk
-
# Bit-level fps in rich edit layer.
UNINITIALIZED READ
name=http://code.google.com/p/drmemory/issues/detail?id=791