On the GPU and GPU FYI waterfall, some tests are failing mid-way with a DCHECK causing the test to fail with "Total tests: n/a".
Example on the GPU FYI waterfall:
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Debug%20%28NVIDIA%29/builds/21223
Example on the GPU waterfall:
https://build.chromium.org/p/chromium.gpu/builders/Win7%20Debug%20%28NVIDIA%29/builds/53892
Example log on the GPU FYI waterfall:
https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.gpu.fyi%2FWin7_Debug__NVIDIA_%2F21223%2F%2B%2Frecipes%2Fsteps%2Fpixel_test_on_NVIDIA_GPU_on_Windows_on_Windows-2008ServerR2-SP1%2F0%2Fstdout
The log ends with the following stack trace:
0018e16c 06d88dc9 0018e194 06d880da 0e805e1c base!base::debug::BreakDebugger+0x17
0018e174 06d880da 0e805e1c 00000034 247a48d7 chrome!?Run@?$Invoker@U?$BindState@P6AXPBDHV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@base@@1@Z$$V@internal@base@@$$A6AXPBDHV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@3@1@Z@internal@base@@SAXPAVBindStateBase@23@$$QAPBD$$QAH$$QAV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@3@3@Z+0x89
0018e194 06d8817b 06d88dc0 0018e224 0018e228 chrome!base::internal::FunctorTraits<void (__cdecl*)(char const *,int,base::BasicStringPiece<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >,base::BasicStringPiece<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >),void>::Invoke<char const *,int,base::BasicStringPiece<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >,base::BasicStringPiece<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >+0x4a
0018e1b0 06d881e9 008bc44c 0018e224 0018e228 chrome!base::internal::InvokeHelper<0,void>::MakeItSo<void (__cdecl*const &)(char const *,int,base::BasicStringPiece<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >,base::BasicStringPiece<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >),char const *,int,base::BasicStringPiece<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >,base::BasicStringPiece<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >+0x4b
0018e1cc 06d88d98 008bc44c 008bc450 00000000 chrome!??$RunImpl@ABQ6AXPBDHV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@base@@1@ZABV?$tuple@$$V@std@@$S@?$Invoker@U?$BindState@P6AXPBDHV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@base@@1@Z$$V@internal@base@@$$A6AXPBDHV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@3@1@Z@internal@base@@CAXABQ6AXPBDHV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@2@1@ZABV?$tuple@$$V@std@@U?$IndexSequence@$S@2@$$QAPBD$$QAH$$QAV32@7@Z+0x49
0018e1f8 101050b4 008bc438 0018e224 0018e228 chrome!?Run@?$Invoker@U?$BindState@P6AXPBDHV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@base@@1@Z$$V@internal@base@@$$A6AXPBDHV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@3@1@Z@internal@base@@SAXPAVBindStateBase@23@$$QAPBD$$QAH$$QAV?$BasicStringPiece@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@3@3@Z+0x58
0018e21c 10103a33 0e805e1c 00000034 247a48d7 base!base::Callback<void __cdecl(char const *,int,base::BasicStringPiece<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >,base::BasicStringPiece<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >),1,1>::Run+0x54
*** WARNING: Unable to verify checksum for gpu.dll
0018e7b8 0e46bd05 00000003 12acb3cf 103fd748 base!logging::LogMessage::~LogMessage+0x383
0018e93c 0e46aecc 00000002 0018e954 0018e990 gpu!base::win::ScopedCOMInitializer::Initialize+0x125
0018e94c 0e46ba82 80010106 00000000 00000000 gpu!base::win::ScopedCOMInitializer::ScopedCOMInitializer+0x1c
robliao@ this looks very related to https://chromium-review.googlesource.com/c/583933 can you TAL? Is there a way to fix the asserts or can we revert the CL while we figure out what is wrong?
Blocking the ScopedComPtr->ComPtr bug on this because the CL didn't have a BUG associated with it.
+cc kbr, piman for pixel wrangling
+cc jmadill: kbr told me you were possibly looking at a related problem.
On the GPU and GPU FYI waterfall, some tests are failing mid-way with a DCHECK causing the test to fail with "Total tests: n/a".
Example on the GPU FYI waterfall:
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Debug%20%28NVIDIA%29/builds/21223
Example on the GPU waterfall:
https://build.chromium.org/p/chromium.gpu/builders/Win7%20Debug%20%28NVIDIA%29/builds/53892
Example log on the GPU FYI waterfall:
https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.gpu.fyi%2FWin7_Debug__NVIDIA_%2F21223%2F%2B%2Frecipes%2Fsteps%2Fpixel_test_on_NVIDIA_GPU_on_Windows_on_Windows-2008ServerR2-SP1%2F0%2Fstdout
The log ends with the following stack trace:
base!logging::LogMessage::~LogMessage+0x383
gpu!base::win::ScopedCOMInitializer::Initialize+0x125
gpu!base::win::ScopedCOMInitializer::ScopedCOMInitializer+0x1c
gpu!gpu::GetDxDiagnostics+0x12
content!ui::GpuService::UpdateGpuInfoPlatform+0x11e
content!ui::GpuService::RequestCompleteGpuInfo+0xd1
content!base::internal::FunctorTraits<void (__thiscall ui::GpuService::*)(b...
content!base::internal::InvokeHelper<1,void>::MakeItSo<void (__thiscall ui:...
content!base::internal::Invoker<base::internal::BindState<void (__thiscall ...
content!base::internal::Invoker<base::internal::BindState<void (__thiscall ...
base!base::Callback<void __cdecl(void),0,0>::Run+0x35
base!base::debug::TaskAnnotator::RunTask+0x1eb
base!base::MessageLoop::RunTask+0x1fc
base!base::MessageLoop::DeferOrRunPendingTask+0x32
base!base::MessageLoop::DoWork+0x112
base!base::MessagePumpDefault::Run+0x90
base!base::MessageLoop::Run+0xbf
base!base::RunLoop::Run+0xba
content!content::GpuMain+0x516
content!content::RunNamedProcessTypeMain+0x87
content!content::ContentMainRunnerImpl::Run+0x195
robliao@ this looks very related to https://chromium-review.googlesource.com/c/583933 can you TAL? Is there a way to fix the asserts or can we revert the CL while we figure out what is wrong?
Blocking the ScopedComPtr->ComPtr bug on this because the CL didn't have a BUG associated with it.
+cc kbr, piman for pixel wrangling
+cc jmadill: kbr told me you were possibly looking at a related problem.
Updated the description to show the relevant part of the stack (the original stack did not include the actual callers).
This is the same as 749309.
It's not clear why this is just failing now. This code should have failed long ago as GpuMain ran under MTA and GetDxDiagnostics is requesting an STA.
Unmerging the bugs because it isn't clear that they have the same root cause, let's keep this one for ScopedComInitializer-related thing and the other one for DirectComposition.
Comment 1 by robliao@chromium.org
, Jul 27 2017