Is this only flaky on viz_content_browsertests?

Yes, only on Viz.

fsamuel@ can you confirm if there's any way to disable the test only on viz?  This is also affecting linux_chromium_rel_ng on the CQ

Fady, can we just add this test to testing/buildbot/filters/viz.content_browsertests.filter to disable only for viz?  (Maybe also to mojo.fyi.viz.content_browsertests.filter?)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e2620c99e69f29346cb2aeb173d558492f3bbf22

commit e2620c99e69f29346cb2aeb173d558492f3bbf22
Author: Tom Anderson <thomasanderson@chromium.org>
Date: Tue Dec 05 02:14:49 2017

Disable flaky CrossSiteIframeBlockedByXFrameOptionsOrCSP on viz

BUG= 790683 
TBR=creis@chromium.org

Change-Id: I9ba4317841f6487795f1fb0676c9dde09f6fe500
Reviewed-on: https://chromium-review.googlesource.com/801264
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#521590}
[modify] https://crrev.com/e2620c99e69f29346cb2aeb173d558492f3bbf22/testing/buildbot/filters/mojo.fyi.viz.content_browsertests.filter
[modify] https://crrev.com/e2620c99e69f29346cb2aeb173d558492f3bbf22/testing/buildbot/filters/viz.content_browsertests.filter

Stack trace of error:

BrowserTestBase received signal: Segmentation fault. Backtrace:
#0 0x000002c87eac base::debug::StackTrace::StackTrace()
#1 0x0000029eb3c2 content::(anonymous namespace)::DumpStackTraceSignalHandler()
#2 0x7f2bb4b1bcb0 <unknown>
#3 0x00000274a967 content::RenderWidgetHostViewChildFrame::SendSurfaceInfoToEmbedderImpl()
#4 0x00000274b5a8 content::RenderWidgetHostViewChildFrame::OnFirstSurfaceActivation()
#5 0x000003c76527 viz::HostFrameSinkManager::OnFirstSurfaceActivation()
#6 0x000001b1f676 viz::mojom::FrameSinkManagerClientStubDispatch::Accept()
#7 0x000002aaaca7 mojo::internal::MultiplexRouter::ProcessIncomingMessage()
#8 0x000002aaa4db mojo::internal::MultiplexRouter::Accept()
#9 0x000002aa2232 mojo::Connector::ReadSingleMessage()
#10 0x000002aa2961 mojo::Connector::ReadAllAvailableMessages()
#11 0x0000031c6fca mojo::SimpleWatcher::OnHandleReady()
#12 0x000002c8921f base::debug::TaskAnnotator::RunTask()
#13 0x000002ca2c47 base::MessageLoop::RunTask()
#14 0x000002ca3168 base::MessageLoop::DoWork()
#15 0x000002ca578f base::(anonymous namespace)::WorkSourceDispatch()
#16 0x7f2bb8bd7e04 g_main_context_dispatch
#17 0x7f2bb8bd8048 <unknown>
#18 0x7f2bb8bd80ec g_main_context_iteration
#19 0x000002ca5652 base::MessagePumpGlib::Run()
#20 0x000002cbf804 base::RunLoop::Run()
#21 0x000002a0507e content::MessageLoopRunner::Run()
#22 0x0000029ebeb0 content::NavigateIframeToURL()
#23 0x00000151c055 content::SitePerProcessBrowserTest_CrossSiteIframeBlockedByXFrameOptionsOrCSP_Test::RunTestOnMainThread()
#24 0x0000029eb0ec content::BrowserTestBase::ProxyRunTestOnMainThreadLoop()
#25 0x000002a5e689 content::ShellBrowserMainParts::PreMainMessageLoopRun()
#26 0x0000024ad351 content::BrowserMainLoop::PreMainMessageLoopRun()
#27 0x0000027e4e27 content::StartupTaskRunner::RunAllTasksNow()
#28 0x0000024ab9bc content::BrowserMainLoop::CreateStartupTasks()
#29 0x0000024b0618 content::BrowserMainRunnerImpl::Initialize()
#30 0x000002a5df09 ShellBrowserMain()
#31 0x000002a28b00 content::ShellMainDelegate::RunProcess()
#32 0x0000023eebc0 content::RunNamedProcessTypeMain()
#33 0x0000023ef5d5 content::ContentMainRunnerImpl::Run()
#34 0x000003d68c9f service_manager::Main()
#35 0x000001bc10e1 content::ContentMain()
#36 0x0000029ead8e content::BrowserTestBase::SetUp()
#37 0x0000029e180e content::ContentBrowserTest::SetUp()
#38 0x00000172f301 testing::Test::Run()
#39 0x00000172fd70 testing::TestInfo::Run()
#40 0x000001730257 testing::TestCase::Run()
#41 0x000001736887 testing::internal::UnitTestImpl::RunAllTests()
#42 0x000001736507 testing::UnitTest::Run()
#43 0x000002a138e2 base::TestSuite::Run()
#44 0x0000029e5167 content::ContentTestLauncherDelegate::RunTestSuite()
#45 0x0000029ff389 content::LaunchTests()
#46 0x0000029e5120 main
#47 0x7f2bb4b06f45 __libc_start_main
#48 0x0000010f602a _start

I think that this is issue 797801 which has since been fixed. I'll test this on the FYI bot to confirm, as it no longer repros locally.