Add BrowserSelectFileDialogTest.OpenCloseFileDialog

build/sanitizers/lsan_suppressions.cc

Index: build/sanitizers/lsan_suppressions.cc
diff --git a/build/sanitizers/lsan_suppressions.cc b/build/sanitizers/lsan_suppressions.cc
index d1c9d22cac3850eb94ecd77b2c45c3268dcce3c5..956b142bc848a2a01fac07d05428b6d146895bfd 100644
--- a/build/sanitizers/lsan_suppressions.cc
+++ b/build/sanitizers/lsan_suppressions.cc
@@ -54,6 +54,9 @@ char kLSanDefaultSuppressions[] =
 // Leaks in swrast_dri.so. http://crbug.com/540042
 "leak:swrast_dri.so\n"
 
+// Leaks in GtkFileChooserDialog. http://crbug.com/537468
+"leak:libgtk-x11-2.0\n"

[msw, 2015/10/22 22:23:05]

Yeah, it should be 'glib2.0-2.32.4', according to the failure:

Direct leak of 32 byte(s) in 1 object(s) allocated from:
    #0 0x515abb in __interceptor_malloc
(/tmp/rundtqsbH/out/Release/interactive_ui_tests+0x515abb)
    #1 0x7f694e6d1a38 in g_malloc /build/buildd/glib2.0-2.32.4/./glib/gmem.c:159

Indirect leak of 25 byte(s) in 1 object(s) allocated from:
    #0 0x515abb in __interceptor_malloc
(/tmp/rundtqsbH/out/Release/interactive_ui_tests+0x515abb)
    #1 0x7f694e6d1a38 in g_malloc /build/buildd/glib2.0-2.32.4/./glib/gmem.c:159

But that's a very wide suppression, which we should try to avoid. Try remove the
suppression altogether and just using either ANNOTATE_LEAKING_OBJECT_PTR or
ANNOTATE_SCOPED_MEMORY_LEAK within the test itself. If neither of those work,
I'll approve the 'glib2.0-2.32.4' suppression.

[joone, 2015/10/23 10:51:42]

ANNOTATE_SCOPED_MEMORY_LEAK works!

+
 // ================ Leaks in Chromium code ================
 // PLEASE DO NOT ADD SUPPRESSIONS FOR NEW LEAKS.
 // Instead, commits that introduce memory leaks should be reverted. Suppressing