New issue
Advanced search Search tips

Issue 864691 link

Starred by 1 user
Status: Duplicate
Merged: issue 864733
Owner: ----
Closed: Jul 17
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"SitePerProcessMemoryThresholdBrowserTest.SitePerProcessEnabled_HighThreshold" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jul 17 
"SitePerProcessMemoryThresholdBrowserTest.SitePerProcessEnabled_HighThreshold" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 4 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyVwsSBUZsYWtlIkxTaXRlUGVyUHJvY2Vzc01lbW9yeVRocmVzaG9sZEJyb3dzZXJUZXN0LlNpdGVQZXJQcm9jZXNzRW5hYmxlZF9IaWdoVGhyZXNob2xkDA.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs

Comment 1 Deleted

Comment 2 by xiaoche...@chromium.org, Jul 17 

[5204:4936:0717/130210.955:FATAL:ref_counted.h(83)] Check failed: CalledOnValidSequence().
Backtrace:
	base::debug::StackTrace::StackTrace [0x03BE62F0+32]
	base::debug::StackTrace::StackTrace [0x03BE5AAD+13]
	logging::LogMessage::~LogMessage [0x03BFF723+83]
	base::subtle::RefCountedBase::Release [0x011B9301+145]
	syncer::BlockingModelTypeStoreImpl::~BlockingModelTypeStoreImpl [0x06EA65DB+59]
	syncer::BlockingModelTypeStoreImpl::`scalar deleting destructor' [0x06EA71FB+11]
	std::unique_ptr<CPDF_Parser::TrailerData,std::default_delete<CPDF_Parser::TrailerData> >::~unique_ptr<CPDF_Parser::TrailerData,std::default_delete<CPDF_Parser::TrailerData> > [0x02750586+22]
	base::internal::BindState<void (__cdecl*)(base::OnceCallback<void __cdecl(std::unique_ptr<policy::URLBlacklist,std::default_delete<policy::URLBlacklist> >)>,std::unique_ptr<policy::URLBlacklist,std::default_delete<policy::URLBlacklist> > *),base::OnceCall [0x0277527B+27]
	base::internal::CallbackBase::~CallbackBase [0x03BE0949+25]
	base::internal::PostTaskAndReplyImpl::PostTaskAndReply [0x04C4EE14+1508]
	base::internal::PostTaskAndReplyImpl::PostTaskAndReply [0x04C4EFF3+1987]
	base::internal::CallbackBase::~CallbackBase [0x03BE0949+25]
	base::internal::IncomingTaskQueue::TriageQueue::Clear [0x04C3B097+375]
	base::MessageLoop::DeletePendingTasks [0x03C08AE5+101]
	base::MessageLoop::~MessageLoop [0x03C0A817+247]
	base::MessageLoopForUI::`scalar deleting destructor' [0x03AFF99B+11]
	content::ContentMainRunnerImpl::Shutdown [0x03B9C31E+222]
	service_manager::Main [0x042A2C2C+1484]
	content::ContentMain [0x03B9B813+51]
	content::BrowserTestBase::SetUp [0x03CEC8A6+1942]
	InProcessBrowserTest::SetUp [0x03CAF786+566]
	testing::Test::Run [0x01DE8860+112]

Comment 3 by xiaoche...@chromium.org, Jul 17 

It's not the test's own issue. Many tests are crashing flakily with the same stack trace.

Comment 4 by xiaoche...@chromium.org, Jul 17

Mergedinto: 864733
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment