is this only impacting caroline?  Were other boards tested?   

Albert, is this consistent with other observed bugs?

All, please triage / assign soon per the M67 schedule.  Thank you

Yes, reproduced only on caroline but not reprod EVE and Kevin.

Thanks Ansar, per our IM I'll block on caroline but unblock on others.

Still need to triage / assign since it's a blocker :-)

abodenha@, do you have thoughts on ownership?  Do we have the right contacts on the bug?  Thanks..

I haven't seen reports of this elsewhere. Suspicious that this isn't actually a UI issue since it only happens on caroline.

I suspect there is a JS error happening in oobe or login. abodeti@ can you upload a feedback report?

Owner to alemate@ who has been making changes in the JS recently.

Plan is to block caroline only for DEV RCs.   Please advise if that's neeeded, etc.

Ping on this bug; caroline missed another DEV.  Can we assign, etc.?

The error was "Renderer crash on login window".
Latest canary does have this problem, but ToT does not.

So to verify that the issue has indeed been fixed, I tried to build the same chrome version locally (via simple chrome workflow). And it stopped failing.

I built chrome with the same SDK version, and it also did not fail. While canary image is indeed failing.

My debug build crashes with known issue : FATAL:render_widget_host_impl.cc(1240)] Check failed: is_in_gesture_scroll_[gesture_event.SourceDevice()].
(See Issue 797322, Issue 806940, Issue 821237,  Issue 827286  for this crash.)

[18160:18160:0403/203017.969013:FATAL:render_widget_host_impl.cc(1240)] Check failed: is_in_gesture_scroll_[gesture_event.SourceDevice()]. 
#0 0x620c3e5a5708 base::debug::StackTrace::StackTrace()
#1 0x620c3e5a3c2c base::debug::StackTrace::StackTrace()
#2 0x620c3e60fdfa logging::LogMessage::~LogMessage()
#3 0x620c38faf1b3 content::RenderWidgetHostImpl::ForwardGestureEventWithLatencyInfo()
#4 0x620c38feff79 content::RenderWidgetHostViewBase::ProcessGestureEvent()
#5 0x620c38fd6aa4 content::RenderWidgetHostInputEventRouter::DispatchTouchpadGestureEvent()
#6 0x620c38fd752b content::RenderWidgetHostInputEventRouter::DispatchEventToTarget()
#7 0x620c39001f99 content::RenderWidgetTargeter::FoundTarget()
#8 0x620c390015f2 content::RenderWidgetTargeter::FindTargetAndDispatch()
#9 0x620c38fd1d24 content::RenderWidgetHostInputEventRouter::RouteTouchpadGestureEvent()
#10 0x620c38fd1b8d content::RenderWidgetHostInputEventRouter::RouteGestureEvent()
#11 0x620c395b7ca0 content::RenderWidgetHostViewEventHandler::OnScrollEvent()
#12 0x620c38fe839b content::RenderWidgetHostViewAura::OnScrollEvent()
#13 0x620c403e6a36 ui::EventHandler::OnEvent()
#14 0x620c403e5d77 ui::EventDispatcher::DispatchEvent()
#15 0x620c403e459e ui::EventDispatcher::ProcessEvent()
#16 0x620c403e3ffc ui::EventDispatcherDelegate::DispatchEventToTarget()
#17 0x620c403e3eb0 ui::EventDispatcherDelegate::DispatchEvent()
#18 0x620c4b3307a1 ui::EventProcessor::OnEventFromSource()
#19 0x620c4b330ae1 ui::EventProcessor::OnEventFromSource()
#20 0x620c403e8c23 ui::EventSource::DeliverEventToSink()
#21 0x620c403e829a ui::EventSource::SendEventToSink()
#22 0x620c4618e0e1 ash::AshWindowTreeHostPlatform::DispatchEvent()
#23 0x620c3680ff90 _ZN4base8internal13FunctorTraitsIMN2ui22PlatformWindowDelegateEFvPNS2_5EventEEvE6InvokeIPS3_JS5_EEEvS7_OT_DpOT0_
#24 0x620c3680febf _ZN4base8internal12InvokeHelperILb0EvE8MakeItSoIMN2ui22PlatformWindowDelegateEFvPNS4_5EventEEJPS5_S7_EEEvOT_DpOT0_
#25 0x620c3680fe32 _ZN4base8internal7InvokerINS0_9BindStateIMN2ui22PlatformWindowDelegateEFvPNS3_5EventEEJNS0_17UnretainedWrapperIS4_EEEEEFvS6_EE7RunImplIS8_NSt3__15tupleIJSA_EEEJLm0EEEEvOT_OT0_NSF_16integer_sequenceImJXspT1_EEEEOS6_
#26 0x620c3680fd46 _ZN4base8internal7InvokerINS0_9BindStateIMN2ui22PlatformWindowDelegateEFvPNS3_5EventEEJNS0_17UnretainedWrapperIS4_EEEEEFvS6_EE7RunOnceEPNS0_13BindStateBaseES6_
#27 0x620c365d017f _ZNO4base12OnceCallbackIFvPN2ui13OzonePlatformEEE3RunES3_
#28 0x620c403ed1da ui::DispatchEventFromNativeUiEvent()
#29 0x620c3680f5f2 ui::DrmWindowHost::DispatchEvent()
#30 0x620c403cb85e ui::PlatformEventSource::DispatchEvent()
#31 0x620c4105aff1 ui::EventFactoryEvdev::DispatchUiEvent()
#32 0x620c4105d35d ui::EventFactoryEvdev::DispatchScrollEvent()
#33 0x620c3672edef _ZN4base8internal13FunctorTraitsIMN11google_apis13RequestSenderEFvRKNS_7WeakPtrINS2_29AuthenticatedRequestInterfaceEEEEvE6InvokeIRKNS4_IS3_EEJS8_EEEvSA_OT_DpOT0_
#34 0x620c367fe855 _ZN4base8internal12InvokeHelperILb1EvE8MakeItSoIRKMN2ui21DrmDisplayHostManagerEFvRKNS_8FilePathEERKNS_7WeakPtrIS5_EEJS8_EEEvOT_OT0_DpOT1_
#35 0x620c4106269d _ZN4base8internal7InvokerINS0_9BindStateIMN2ui17EventFactoryEvdevEFvRKNS3_17ScrollEventParamsEEJNS_7WeakPtrIS4_EES5_EEEFvvEE7RunImplIRKS9_RKNSt3__15tupleIJSB_S5_EEEJLm0ELm1EEEEvOT_OT0_NSI_16integer_sequenceImJXspT1_EEEE
#36 0x620c410625ac _ZN4base8internal7InvokerINS0_9BindStateIMN2ui17EventFactoryEvdevEFvRKNS3_17ScrollEventParamsEEJNS_7WeakPtrIS4_EES5_EEEFvvEE3RunEPNS0_13BindStateBaseE
#37 0x620c357ca5fc _ZNO4base12OnceCallbackIFvvEE3RunEv
#38 0x620c3e5a8c05 base::debug::TaskAnnotator::RunTask()
#39 0x620c3e83a449 base::internal::IncomingTaskQueue::RunTask()
#40 0x620c3e62827b base::MessageLoop::RunTask()
#41 0x620c3e628528 base::MessageLoop::DeferOrRunPendingTask()
#42 0x620c3e628838 base::MessageLoop::DoWork()
#43 0x620c3e62cf70 base::MessagePumpLibevent::Run()
#44 0x620c3e627a3c base::MessageLoop::Run()
#45 0x620c3e6c2ffd base::RunLoop::Run()
#46 0x620c3d7f24a1 ChromeBrowserMainParts::MainMessageLoopRun()
#47 0x620c38322df1 content::BrowserMainLoop::RunMainMessageLoopParts()
#48 0x620c3832c680 content::BrowserMainRunnerImpl::Run()
#49 0x620c38315c81 content::BrowserMain()
#50 0x620c3d79ba63 content::RunNamedProcessTypeMain()
#51 0x620c3d79e991 content::ContentMainRunnerImpl::Run()
#52 0x620c3d794125 content::ContentServiceManagerMainDelegate::RunEmbedderProcess()
#53 0x620c3d7c7894 service_manager::Main()
#54 0x620c3d79a853 content::ContentMain()
#55 0x620c35542352 ChromeMain
#56 0x620c35542242 main
#57 0x795108038736 __libc_start_main
#58 0x620c355420e9 _start

marcheu@ pointed me to the  Issue 827188 , which might also affect this device, but the latter is fixed in ToT.

It doesn't happen for in ToT. So it might be some strange race in the renderer. Or it may be already fixed.

... for me ...

Caroline is also prone to the  issue 827188 , which came up with chrome pinning last Wednesday. So my plan is to wait for the new uprev to get  issue 827188  fixed.

We upreved recently.  Possible to retest with ToT to unblock dev?

Issue still reproducible on AU to ToT build 10559.0.0, 67.0.3390.0

 Issue 830817  has been merged into this issue.

 Issue 832532  has been merged into this issue.

Issue seems to repro for Daisy, Peppy,Kip and Reks as per  issue 832532 

C#23>

Correction in update in  issue 832532  
Issue seems to be repro only on Daisy and doesn't repro on Peppy,Kip and Reks for build  67.0.3393.4/10569.1.0

Below are Good and Bad Builds:
Good Build : 67.0.3390.0/10562.0.0 
Bad Build :  67.0.3393.4/10569.1.0

Able to repro Issue on latest M-67 67.0.3396.0/10575.2.0

Thanks..!!

Want to be clear; bug is only impacting daisy now?  No longer impacting caroline?

Seeing this issue on Terra with build version: 10575.3.0/67.0.3396.0.  No OOBE screen is seen after successful recovery with USB stick.  

Terra was being built with clang CFI enabled which was causing a renderer crash on login. That has been disabled and may fix this issue.

Scope of bug is daisy and maybe terra?  Need to get a definitive answer to partially unblock dev

I just verified that last Caroline build boots successfully. So it was a duplicate of 830321.

This bug began before  bug 830321  was introduced.  So it wasn't
a duplicate.  However, caroline and terra were broken for an
apparently unrelated reason until two builds before, and that
bug was fixed.  So, meh.

For clarity:  This bug seems to be an agglomeration of multiple
different problems that occurred at different times.  At minimum,
it was confused with two distinct bugs on caroline and terra, as
well as some bugs on ARM platforms.  Both of the caroline+terra
bugs are now fixed.  I can't speak to failures on ARM.

I verified that 67.0.3396.0 is broken, and https://chromium.googlesource.com/chromium/src.git/+/bff9e2df3f45399aa207d9e380da1716e2435fe8 fixes it. It should already be in the next branch build.