New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 704427 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

FATAL:event_with_latency_info.h(53)] Check failed: other.latency.trace_id() > latency.trace_id()

Project Member Reported by alemate@chromium.org, Mar 23 2017

Issue description

Debug Chrome crashes on ChromeOS OOBE after start on samus with :

[15416:15416:0322/225415.731997:FATAL:event_with_latency_info.h(53)] Check failed: other.latency.trace_id() > latency.trace_id() (25769803905 vs. 25769803906)
#0 0x5ce02c8ae6b1 base::debug::StackTrace::StackTrace()
#1 0x5ce02c8ac809 base::debug::StackTrace::StackTrace()
#2 0x5ce02c8f305b logging::LogMessage::~LogMessage()
#3 0x5ce028ccd349 content::EventWithLatencyInfo<>::CoalesceWith()
#4 0x5ce028ccb5a3 content::GestureEventQueue::QueueScrollOrPinchAndForwardIfNecessary()
#5 0x5ce028cca67d content::GestureEventQueue::QueueAndForwardIfNecessary()
#6 0x5ce028cca160 content::GestureEventQueue::QueueEvent()
#7 0x5ce028cd26e9 content::InputRouterImpl::SendGestureEvent()
#8 0x5ce028e518fc content::RenderWidgetHostImpl::ForwardGestureEventWithLatencyInfo()
#9 0x5ce028e830ab content::RenderWidgetHostViewAura::ProcessGestureEvent()
#10 0x5ce028e7542d content::RenderWidgetHostInputEventRouter::RouteTouchscreenGestureEvent()
#11 0x5ce028e72b95 content::RenderWidgetHostInputEventRouter::RouteGestureEvent()
#12 0x5ce0292a08be content::RenderWidgetHostViewEventHandler::OnGestureEvent()
#13 0x5ce028e832f4 content::RenderWidgetHostViewAura::OnGestureEvent()
#14 0x5ce02e1a34bb ui::EventHandler::OnEvent()
#15 0x5ce02e19fd41 ui::EventDispatcher::DispatchEvent()
#16 0x5ce02e19f7b7 ui::EventDispatcher::ProcessEvent()
#17 0x5ce02e19f397 ui::EventDispatcherDelegate::DispatchEventToTarget()
#18 0x5ce02e19f1d6 ui::EventDispatcherDelegate::DispatchEvent()
#19 0x5ce02f27cc19 aura::WindowEventDispatcher::ProcessGestures()
#20 0x5ce02f27c1b3 aura::WindowEventDispatcher::ProcessedTouchEvent()
#21 0x5ce028e808ef content::RenderWidgetHostViewAura::ProcessAckedTouchEvent()
#22 0x5ce028e575dd content::RenderWidgetHostImpl::OnTouchEventAck()
#23 0x5ce028cd33b1 content::InputRouterImpl::OnTouchEventAck()
#24 0x5ce028ceac73 content::PassthroughTouchEventQueue::AckTouchEventToClient()
#25 0x5ce028ceaba1 content::PassthroughTouchEventQueue::AckCompletedEvents()
#26 0x5ce028cea5cc content::PassthroughTouchEventQueue::ProcessTouchAck()
#27 0x5ce028cd4e9c content::InputRouterImpl::ProcessTouchAck()
#28 0x5ce028cd4a55 content::InputRouterImpl::ProcessInputEventAck()
#29 0x5ce028cd41c4 content::InputRouterImpl::OnInputEventAck()
#30 0x5ce027a2c792 _ZN4base20DispatchToMethodImplIPN2ui21DrmThreadMessageProxyEMS2_FvRKNS_8FilePathEERKSt5tupleIJS4_EEJLm0EEEEvRKT_T0_OT1_NS_13IndexSequenceIJXspT2_EEEE
#31 0x5ce028cd8d32 _ZN4base16DispatchToMethodIPN7content15InputRouterImplEMS2_FvRKNS1_13InputEventAckEERKSt5tupleIJS4_EEEEvRKT_T0_OT1_
#32 0x5ce028cd7b81 _ZN3IPC16DispatchToMethodIN7content15InputRouterImplEMS2_FvRKNS1_13InputEventAckEEvSt5tupleIJS3_EEEEvPT_T0_PT1_RKT2_
#33 0x5ce028cd6405 _ZN3IPC8MessageTI38InputHostMsg_HandleInputEvent_ACK_MetaSt5tupleIJN7content13InputEventAckEEEvE8DispatchINS3_15InputRouterImplES8_vMS8_FvRKS4_EEEbPKNS_7MessageEPT_PT0_PT1_T2_
#34 0x5ce028cd2bea content::InputRouterImpl::OnMessageReceived()
#35 0x5ce028e4f65d content::RenderWidgetHostImpl::OnMessageReceived()
#36 0x5ce028e02259 content::RenderProcessHostImpl::OnMessageReceived()
#37 0x5ce02d6e1520 IPC::ChannelProxy::Context::OnDispatchMessage()
#38 0x5ce02d6e7e0e _ZN4base8internal13FunctorTraitsIMN3IPC12ChannelProxy7ContextEFvRKNS2_7MessageEEvE6InvokeIRK13scoped_refptrIS4_EJS7_EEEvS9_OT_DpOT0_
#39 0x5ce02d6e778f _ZN4base8internal12InvokeHelperILb0EvE8MakeItSoIRKMN3IPC12ChannelProxy7ContextEFvRKNS4_7MessageEEJRK13scoped_refptrIS6_ES9_EEEvOT_DpOT0_
#40 0x5ce02d6e5d6d _ZN4base8internal7InvokerINS0_9BindStateIMN3IPC12ChannelProxy7ContextEFvRKNS3_7MessageEEJ13scoped_refptrIS5_ES6_EEEFvvEE7RunImplIRKSA_RKSt5tupleIJSC_S6_EEJLm0ELm1EEEEvOT_OT0_NS_13IndexSequenceIJXspT1_EEEE
#41 0x5ce02d6e4e69 _ZN4base8internal7InvokerINS0_9BindStateIMN3IPC12ChannelProxy7ContextEFvRKNS3_7MessageEEJ13scoped_refptrIS5_ES6_EEEFvvEE3RunEPNS0_13BindStateBaseE
#42 0x5ce027b897e0 _ZNO4base8internal8RunMixinINS_8CallbackIFvvELNS0_8CopyModeE0ELNS0_10RepeatModeE0EEEE3RunEv
#43 0x5ce02cac1c05 base::debug::TaskAnnotator::RunTask()
#44 0x5ce02c91260f base::MessageLoop::RunTask()
#45 0x5ce02c91277e base::MessageLoop::DeferOrRunPendingTask()
#46 0x5ce02c912cca base::MessageLoop::DoWork()
#47 0x5ce02c92bf8c base::MessagePumpLibevent::Run()
#48 0x5ce02c9121ba base::MessageLoop::RunHandler()
#49 0x5ce02c99ea61 base::RunLoop::Run()
#50 0x5ce02bcb5563 ChromeBrowserMainParts::MainMessageLoopRun()
#51 0x5ce0285df404 content::BrowserMainLoop::RunMainMessageLoopParts()
#52 0x5ce0285e9861 content::BrowserMainRunnerImpl::Run()
#53 0x5ce0285db020 content::BrowserMain()
#54 0x5ce02bb8d359 content::RunNamedProcessTypeMain()
#55 0x5ce02bb8e19a content::ContentMainRunnerImpl::Run()
#56 0x5ce02bb8c5e3 content::ContentServiceManagerMainDelegate::Run()
#57 0x5ce02f1fb47b service_manager::Main()
#58 0x5ce02bb8c963 content::ContentMain()
#59 0x5ce027351bb7 ChromeMain
#60 0x5ce027351a80 main
#61 0x7947fbbcc816 __libc_start_main

 
Cc: r...@chromium.org
Cc: chongz@chromium.org
Labels: Needs-Bisect
Does this only happen in the OOBE?

Looks like we're reordering scroll/pinch events.
Components: Blink>Input
alemate@ is this still reproducible?
alemate@ appreciate if you can respond would save us building a Chrome OS build to test.

Comment 6 by r...@chromium.org, Sep 7 2017

Cc: abodenha@chromium.org
dtapuska@ do you not already test all your changes on Chrome OS?

If not, could you tell us what pain points you experience preventing you from building and testing Chrome for Chrome OS. Are you familiar with the http://go/simplechrome workflow?

krc@ no I don't frequently test on a Chrome OS device usually Linux, Mac, and Windows. Yes I'm familiar with the simplechrome workflow but it still will take me some time to download a recent image, flash it and the build my own copy to test. No worries I was just asking a question; this has been a P1 since March so I don't suspect that it still an issue.
Status: WontFix (was: Untriaged)
Closing as can't repro. I've build link against R63-9916.0.0 with dchecks on and can go through the OOBE using the touchscreen.

Sign in to add a comment