Change LSan suppressions from 'WebCore' to 'blink'.

tools/lsan/suppressions.txt

 # HeapCheck sanity test
 leak:base::ToolsSanityTest_MemoryLeak_Test::TestBody
 
 #### Third-party leaks ####
 
 # False positives in libfontconfig. http://crbug.com/39050
 leak:libfontconfig
 
 # Leaks in Nvidia's libGL.
 leak:libGL.so
 
 # A small string is leaked here (57 bytes per process). http://crbug.com/46571#c9
-leak:WebCore::V8GCController::collectGarbage
+leak:blink::V8GCController::collectGarbage
 
 # http://crbug.com/270180
 leak:net::ProxyResolverV8::Context::ResolveProxy
 
 # NSS leaks in CertDatabaseNSSTest tests. http://crbug.com/51988
 leak:net::NSSCertDatabase::ImportFromPKCS12
 leak:net::NSSCertDatabase::ListCerts
 leak:net::NSSCertDatabase::DeleteCertAndKey
 leak:crypto::ScopedTestNSSDB::ScopedTestNSSDB
 # Another leak due to not shutting down NSS properly. http://crbug.com/124445
@@ skipping 20 matching lines @@
 # V8 may leak this by design in unit tests. http://crbug.com/323149
 leak:v8::internal::Genesis::Genesis
 
 # Suppressions for objects which can be owned by the V8 heap. This is a
 # temporary workaround until LeakSanitizer supports the V8 heap.
 # Those should only fire in (browser)tests. If you see one of them in Chrome,
 # then it's a real leak.
 # http://crbug.com/328552
 leak:WTF::StringImpl::createUninitialized
 leak:WTF::StringImpl::create8BitIfPossible
-leak:WebCore::MouseEvent::create
-leak:WebCore::V8WindowShell::initializeIfNeeded
-leak:WebCore::*::*GetterCallback
-leak:WebCore::CSSComputedStyleDeclaration::create
-leak:WebCore::V8PerIsolateData::ensureDomInJSContext
+leak:blink::MouseEvent::create
+leak:blink::V8WindowShell::initializeIfNeeded
+leak:blink::*::*GetterCallback
+leak:blink::CSSComputedStyleDeclaration::create
+leak:blink::V8PerIsolateData::ensureDomInJSContext
 
 # http://crbug.com/356785
 leak:content::RenderViewImplTest_DecideNavigationPolicyForWebUI_Test::TestBody
 
 #### Actual bugs in Chromium code ####
 # PLEASE DO NOT ADD SUPPRESSIONS FOR NEW LEAKS.
 # Instead, commits that introduce memory leaks should be reverted. Suppressing
 # the leak is acceptable in some cases when reverting is impossible, i.e. when
 # enabling leak detection for the first time for a test target with pre-existing
 # leaks.
@@ skipping 15 matching lines @@
 
 # http://crbug.com/356306
 leak:content::SetProcessTitleFromCommandLine
 
 # http://crbug.com/354881
 leak:LoginUtilsBlockingLoginTest_LoginBlocksForUser
 leak:LoginUtilsTest::SetUp
 leak:LoginUtilsTest::PrepareProfile
 
 # PLEASE READ ABOVE BEFORE ADDING NEW SUPPRESSIONS.