Disable BrowserInitiatedSingleDump Android+ASAN

Disable SingleProcessMemoryTracingTest.BrowserInitiatedSingleDump on
Android+ASAN.

TBR=primiano@chromium.org

Bug: 788788
Change-Id: I8ec8168ff962a7faad1617b21cf797a654f14adf
Reviewed-on: https://chromium-review.googlesource.com/815955Reviewed-by: Shimi Zhang <ctzsm@chromium.org>
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#522647}

content/browser/tracing/memory_tracing_browsertest.cc

@@ -185,10 +185,17 @@ class SingleProcessMemoryTracingTest : public MemoryTracingTest {
   }
 };
 
+// https://crbug.com/788788
+#if defined(OS_ANDROID) && defined(ADDRESS_SANITIZER)
+#define MAYBE_BrowserInitiatedSingleDump DISABLED_BrowserInitiatedSingleDump
+#else
+#define MAYBE_BrowserInitiatedSingleDump BrowserInitiatedSingleDump
+#endif  // defined(OS_ANDROID) && defined(ADDRESS_SANITIZER)
+
 // Checks that a memory dump initiated from a the main browser thread ends up in
 // a single dump even in single process mode.
 IN_PROC_BROWSER_TEST_F(SingleProcessMemoryTracingTest,
-                       BrowserInitiatedSingleDump) {
+                       MAYBE_BrowserInitiatedSingleDump) {
   Navigate(shell());
 
   EXPECT_CALL(*mock_dump_provider_, OnMemoryDump(_,_)).WillOnce(Return(true));