Suppress a few simple leaks found by Dr. Memory

tools/valgrind/drmemory/suppressions.txt

Index: tools/valgrind/drmemory/suppressions.txt
===================================================================
--- tools/valgrind/drmemory/suppressions.txt	(revision 95980)
+++ tools/valgrind/drmemory/suppressions.txt	(working copy)
@@ -657,6 +657,11 @@
 *!TestURLRequestContextGetter::GetURLRequestContext
 *!URLFetcher::Core::StartURLRequest
 
+# This test intentionally leaks an object and checks that it's never deleted
+LEAK
+...
+*!BrowserThreadTest_NotReleasedIfTargetThreadNonExistent_Test::TestBody
+
 ############################
 # Real issues in Chromium
 
@@ -751,6 +756,15 @@
 *!TestingProfile::CreateRequestContext
 *!*ProfileSyncService*::SetUp
 
+# http://crbug.com/78784
+LEAK
+...
+*!RenderWidgetHost::WasHidden
+
+LEAK
+...
+*!RenderWidgetHost::WasRestored
+
 # http://crbug.com/81522
 LEAK
 *!operator new
@@ -836,6 +850,11 @@
 *!browser_sync::WeakHandle<browser_sync::JsBackend>::*
 *!sync_api::SyncManager::SyncInternal::Init
 
+# http://crbug.com/91491
+LEAK
+...
+*!CrxUpdateService::ProcessPendingItems
+
 # http://crbug.com/92026
 UNINITIALIZED READ
 softokn3.dll!FC_GetFunctionList
@@ -852,5 +871,10 @@
 ...
 *!`anonymous namespace'::ConflictingDllsTest::ExecuteImpl
 
+# http://crbug.com/92150
+LEAK
+...
+*!BookmarkEditorView::Init
+
 # Empty line at EOF - workaround for
 # http://code.google.com/p/drmemory/issues/detail?id=41