summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorerg@google.com <erg@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2009-07-23 17:44:52 +0000
committererg@google.com <erg@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2009-07-23 17:44:52 +0000
commitdcf998001a3742efd7b52ee73a44f47dcce97c58 (patch)
treedae350ae3741c39cb950e51a1018bf8301e7c405 /tools
parentac8d344116b12cad0ba81179746a0cd0b487a698 (diff)
downloadchromium_src-dcf998001a3742efd7b52ee73a44f47dcce97c58.zip
chromium_src-dcf998001a3742efd7b52ee73a44f47dcce97c58.tar.gz
chromium_src-dcf998001a3742efd7b52ee73a44f47dcce97c58.tar.bz2
Revert "Remove suppressions that don't reproduce."
It turns out while I couldn't reproduce these valgrind errors locally, they reproduce on the buildbot. This reverts commit dd24218ae59e4c9665c6ebf9fa4ebb5784bf3d88 (r21396). http://crbug.com/16089 TBR=dank Review URL: http://codereview.chromium.org/160023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@21403 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools')
-rw-r--r--tools/valgrind/memcheck/suppressions.txt18
1 files changed, 18 insertions, 0 deletions
diff --git a/tools/valgrind/memcheck/suppressions.txt b/tools/valgrind/memcheck/suppressions.txt
index 5818a12..26b7fc6 100644
--- a/tools/valgrind/memcheck/suppressions.txt
+++ b/tools/valgrind/memcheck/suppressions.txt
@@ -622,6 +622,24 @@
}
{
# very common in ui tests
+ bug_16089
+ Memcheck:Leak
+ fun:*
+ fun:_ZN4base22LinuxDynamicThreadPool8PostTaskEP4Task
+ ...
+ fun:_ZN3net12HostResolver3Job5StartEv
+}
+{
+ # ditto, but tweaked to fire on bots, more robust against optimizer changes?
+ bug_16089b
+ Memcheck:Leak
+ fun:_Znwj
+ fun:_ZN4base22LinuxDynamicThreadPool8PostTaskEP4Task
+ ...
+ fun:_ZN18chrome_browser_net9DnsMaster24PreLockedScheduleLookupsEv
+}
+{
+ # very common in ui tests
bug_16091
Memcheck:Leak
...