Update from https://crrev.com/328418

build/sanitizers/lsan_suppressions.cc

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // This file contains the default suppressions for LeakSanitizer.
 // You can also pass additional suppressions via LSAN_OPTIONS:
 // LSAN_OPTIONS=suppressions=/path/to/suppressions. Please refer to
 // http://dev.chromium.org/developers/testing/leaksanitizer for more info.
 
 #if defined(LEAK_SANITIZER)
@@ skipping 48 matching lines @@
 "leak:WTF::StringImpl::createUninitialized\n"
 "leak:WTF::StringImpl::create8BitIfPossible\n"
 "leak:blink::MouseEvent::create\n"
 "leak:blink::WindowProxy::initializeIfNeeded\n"
 "leak:blink::*::*GetterCallback\n"
 "leak:blink::CSSComputedStyleDeclaration::create\n"
 "leak:blink::V8PerIsolateData::ensureDomInJSContext\n"
 "leak:gin/object_template_builder.h\n"
 "leak:gin::internal::Dispatcher\n"
 "leak:blink::LocalDOMWindow::getComputedStyle\n"
+// This should really be RemoteDOMWindow::create, but symbolization is
+// weird in release builds. https://crbug.com/484760
+"leak:blink::RemoteFrame::create\n"
 
 // http://crbug.com/356785
 "leak:content::RenderViewImplTest_DecideNavigationPolicyForWebUI_Test::TestBody\n"
 
 // ================ Leaks 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 12 matching lines @@
 
 // http://crbug.com/356306
 "leak:content::SetProcessTitleFromCommandLine\n"
 
 // PLEASE READ ABOVE BEFORE ADDING NEW SUPPRESSIONS.
 
 // End of suppressions.
 ;  // Please keep this semicolon.
 
 #endif  // LEAK_SANITIZER