summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorbrettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-12-07 17:24:30 +0000
committerbrettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-12-07 17:24:30 +0000
commita47105c838e106ca54496e9767371762bce4e246 (patch)
tree53b31d4922e86d57be116c124ca134d977310265 /tools
parent5b466f0add1032cd825f3f2cb492b29b1ed45cc3 (diff)
downloadchromium_src-a47105c838e106ca54496e9767371762bce4e246.zip
chromium_src-a47105c838e106ca54496e9767371762bce4e246.tar.gz
chromium_src-a47105c838e106ca54496e9767371762bce4e246.tar.bz2
Initialize the CPU usage variable.
I'm not sure why it's causing valgrind errors, since the IPC system should always be writing the variable. But it's probably good practice to initialize it anyway. BUG=106067 TEST= Review URL: http://codereview.chromium.org/8773018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@113408 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools')
-rw-r--r--tools/valgrind/memcheck/suppressions.txt6
1 files changed, 0 insertions, 6 deletions
diff --git a/tools/valgrind/memcheck/suppressions.txt b/tools/valgrind/memcheck/suppressions.txt
index 72695b7..a953bfa 100644
--- a/tools/valgrind/memcheck/suppressions.txt
+++ b/tools/valgrind/memcheck/suppressions.txt
@@ -5238,12 +5238,6 @@
fun:_ZN7WebCore15HTMLTreeBuilder16processCharacterERNS_15AtomicHTMLTokenE
}
{
- bug_106067
- Memcheck:Uninitialized
- fun:_ZN16RenderThreadImpl26IdleHandlerInForegroundTabEv
- fun:_ZN16RenderThreadImpl11IdleHandlerEv
-}
-{
bug_106104
Memcheck:Unaddressable
...