New issue
Advanced search Search tips

Issue 876903 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Aug 23
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

browser_tests OutOfProcessPPAPITest.View_CreateInvisible

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Aug 22

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of skym@chromium.org

browser_tests OutOfProcessPPAPITest.View_CreateInvisible

Builders failed on: 
- Win7 Tests (1): 
  https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win7%20Tests%20%281%29


 
Cc: lukasza@chromium.org
First flake of OutOfProcessPPAPITest.View_CreateInvisible at 11:52:11 AM PDT

https://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=OutOfProcessPPAPITest.View_CreateInvisible

I've asked lukasza@ to check if https://chromium-review.googlesource.com/c/chromium/src/+/1178885 might be related, I don't understand much of the code here so I'm having a difficult time speculating.
The test flakily crashes on Windows platforms only.  Example from https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8937468833869241008/+/steps/browser_tests_on_Windows-10-15063/0/logs/OutOfProcessPPAPITest.View_CreateInvisible/0:

Received fatal exception EXCEPTION_ACCESS_VIOLATION
Backtrace:
	std::_Tree<std::_Tmap_traits<content::RenderProcessHostImpl * __ptr64,base::Time,std::less<content::RenderProcessHostImpl * __ptr64>,std::allocator<std::pair<content::RenderProcessHostImpl * __ptr64 const,base::Time> >,0> >::emplace<content::RenderProcess [0x00007FF7422F0C1D+189]
	base::debug::TaskAnnotator::RunTask [0x00007FF7441669AC+300]
	base::MessageLoop::RunTask [0x00007FF743192BFF+223]
	base::MessageLoop::DoWork [0x00007FF743192FF5+389]
	base::MessagePumpForUI::DoRunLoop [0x00007FF7431943A9+169]
	base::MessagePumpWin::Run [0x00007FF743193E4E+78]
	base::RunLoop::Run [0x00007FF7431B55E1+49]
	InProcessBrowserTest::QuitBrowsers [0x00007FF74322FC7C+220]
	InProcessBrowserTest::PostRunTestOnMainThread [0x00007FF74322FB4A+42]
	content::BrowserTestBase::ProxyRunTestOnMainThreadLoop [0x00007FF7433C8DEF+879]
	ChromeBrowserMainParts::PreMainMessageLoopRunImpl [0x00007FF74419BB24+4772]
	ChromeBrowserMainParts::PreMainMessageLoopRun [0x00007FF74419A76E+174]
	content::BrowserMainLoop::PreMainMessageLoopRun [0x00007FF742076A65+85]
	content::StartupTaskRunner::RunAllTasksNow [0x00007FF7423A591B+43]
	content::BrowserMainLoop::CreateStartupTasks [0x00007FF742075318+616]
	content::BrowserMainRunnerImpl::Initialize [0x00007FF74207916E+126]
	content::BrowserMain [0x00007FF742073260+176]
	content::RunBrowserProcessMain [0x00007FF7431267EF+111]
	content::ContentMainRunnerImpl::Run [0x00007FF7431270D3+483]
	service_manager::Main [0x00007FF74390186E+782]
	content::ContentMain [0x00007FF743126721+65]
	content::BrowserTestBase::SetUp [0x00007FF7433C8969+1785]
	InProcessBrowserTest::SetUp [0x00007FF74322E97C+556]
	testing::Test::Run [0x00007FF74162A760+112]
Let's speculatively revert and see if this helps - this is probably faster and easier than building and trying the test on Windows.
Status: Fixed (was: Available)
It looks no longer flaky to me. Closing

Sign in to add a comment