summaryrefslogtreecommitdiffstats
path: root/base/utf_string_conversion_utils.cc
diff options
context:
space:
mode:
authorbryner@chromium.org <bryner@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-07-30 20:52:36 +0000
committerbryner@chromium.org <bryner@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-07-30 20:52:36 +0000
commitdd9b904b47f8c529e20e9f4f87d8f019e2a594bc (patch)
tree93ebdbf2b428bf6ce7210c7cf7be1271a3441fba /base/utf_string_conversion_utils.cc
parent1bc6c551f14f237d5d56b18afb87ea1570483c1c (diff)
downloadchromium_src-dd9b904b47f8c529e20e9f4f87d8f019e2a594bc.zip
chromium_src-dd9b904b47f8c529e20e9f4f87d8f019e2a594bc.tar.gz
chromium_src-dd9b904b47f8c529e20e9f4f87d8f019e2a594bc.tar.bz2
Initialize salt_ to zero in VisitedLinkCommon.
Previously, this memory would remain uninitialized until the renderer received a VisitedLink_NewTable message. This was causing valgrind errors in PhishingDOMFeatureExtractorTest when WebKit computed URL fingerprints, since the test never sends a VisitedLink_NewTable message. BUG=none TEST=no valgrind errors in PhishingDOMFeatureExtractorTest Review URL: http://codereview.chromium.org/2873081 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54376 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/utf_string_conversion_utils.cc')
0 files changed, 0 insertions, 0 deletions