New issue
Advanced search Search tips

Issue 610922 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Jan 10
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

FATAL:inter_process_time_ticks_converter.cc(21)] Check failed: target_range >= 0 (-72801 vs. 0)

Project Member Reported by ukai@chromium.org, May 11 2016

Issue description

Version: 52.0.2731.0 (Developer Build) (64-bit) with dcheck_always_on=1
OS: Linux

What steps will reproduce the problem?
(1) https://plus.google.com/
(2) scroll down for a while
(3)

What is the expected output?

What do you see instead?
occasionally, the tab crashed with the following assertion error.

[1:1:0511/112803:FATAL:inter_process_time_ticks_converter.cc(21)] Check failed: 
target_range >= 0 (-72801 vs. 0)
#0 0x7ffff7c8b66e base::debug::StackTrace::StackTrace()
#1 0x7ffff7cabd4b logging::LogMessage::~LogMessage()
#2 0x7ffff54e6f6b content::InterProcessTimeTicksConverter::InterProcessTimeTicksConverter()
#3 0x7ffff53f4c24 content::ResourceDispatcher::ToResourceResponseInfo()
#4 0x7ffff53f4938 content::ResourceDispatcher::OnReceivedResponse()
#5 0x7ffff53f71dd _ZN3IPC8MessageTI33ResourceMsg_ReceivedResponse_MetaSt5tupleIJiN7content20ResourceResponseHeadEEEvE8DispatchINS3_18ResourceDispatcherES8_vMS8_FviRKS4_EEEbPKNS_7MessageEPT_PT0_PT1_T2_
#6 0x7ffff53f4386 content::ResourceDispatcher::DispatchMessage()
#7 0x7ffff53f3c98 content::ResourceDispatcher::OnMessageReceived()
#8 0x7fffede9e3bf _ZN4base8internal7InvokerINS_13IndexSequenceIJLm0EEEENS0_9BindStateINS0_15RunnableAdapterIPFvSt10unique_ptrIN5blink13WebTaskRunner4TaskESt14default_deleteIS9_EEEEESD_JNS0_13PassedWrapperISC_EEEEENS0_12InvokeHelperILb0EvSF_EEFvvEE3RunEPNS0_13BindStateBaseE
#9 0x7ffff7c8c879 base::debug::TaskAnnotator::RunTask()
#10 0x7fffede91327 scheduler::TaskQueueManager::ProcessTaskFromWorkQueue()
#11 0x7fffede900a5 scheduler::TaskQueueManager::DoWork()
#12 0x7fffede922f4 _ZN4base8internal7InvokerINS_13IndexSequenceIJLm0ELm1ELm2EEEENS0_9BindStateINS0_15RunnableAdapterIMN9scheduler16TaskQueueManagerEFvNS_9TimeTicksEbEEEFvPS7_S8_bEJNS_7WeakPtrIS7_EERS8_bEEENS0_12InvokeHelperILb1EvSB_EEFvvEE3RunEPNS0_13BindStateBaseE
#13 0x7ffff7c8c879 base::debug::TaskAnnotator::RunTask()
#14 0x7ffff7cb61c5 base::MessageLoop::RunTask()
#15 0x7ffff7cb64f8 base::MessageLoop::DeferOrRunPendingTask()
#16 0x7ffff7cb6a9c base::MessageLoop::DoDelayedWork()
#17 0x7ffff7cb818d base::MessagePumpDefault::Run()
#18 0x7ffff7cb5cf1 base::MessageLoop::RunHandler()
#19 0x7ffff7ce49a0 base::RunLoop::Run()
#20 0x7ffff7cb4e00 base::MessageLoop::Run()
#21 0x7ffff5efdb72 content::RendererMain()
#22 0x7ffff6015c1e content::RunZygote()
#23 0x7ffff60164b2 content::RunNamedProcessTypeMain()
#24 0x7ffff6016f03 content::ContentMainRunnerImpl::Run()
#25 0x7ffff60157e0 content::ContentMain()
#26 0x555555a2b42b ChromeMain
#27 0x7fffeeb22ec5 __libc_start_main
#28 0x555555a2b309 <unknown>

Received signal 6
#0 0x7ffff7c8b207 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#1 0x7ffff0174340 <unknown>
#2 0x7fffeeb37cc9 gsignal
#3 0x7fffeeb3b0d8 abort
#4 0x7ffff7c89b32 base::debug::BreakDebugger()
#5 0x7ffff7cac00a logging::LogMessage::~LogMessage()
#6 0x7ffff54e6f6b content::InterProcessTimeTicksConverter::InterProcessTimeTicksConverter()
#7 0x7ffff53f4c24 content::ResourceDispatcher::ToResourceResponseInfo()
#8 0x7ffff53f4938 content::ResourceDispatcher::OnReceivedResponse()
#9 0x7ffff53f71dd _ZN3IPC8MessageTI33ResourceMsg_ReceivedResponse_MetaSt5tupleIJiN7content20ResourceResponseHeadEEEvE8DispatchINS3_18ResourceDispatcherES8_vMS8_FviRKS4_EEEbPKNS_7MessageEPT_PT0_PT1_T2_
#10 0x7ffff53f4386 content::ResourceDispatcher::DispatchMessage()
#11 0x7ffff53f3c98 content::ResourceDispatcher::OnMessageReceived()
#12 0x7fffede9e3bf _ZN4base8internal7InvokerINS_13IndexSequenceIJLm0EEEENS0_9BindStateINS0_15RunnableAdapterIPFvSt10unique_ptrIN5blink13WebTaskRunner4TaskESt14default_deleteIS9_EEEEESD_JNS0_13PassedWrapperISC_EEEEENS0_12InvokeHelperILb0EvSF_EEFvvEE3RunEPNS0_13BindStateBaseE
#13 0x7ffff7c8c879 base::debug::TaskAnnotator::RunTask()
#14 0x7fffede91327 scheduler::TaskQueueManager::ProcessTaskFromWorkQueue()
#15 0x7fffede900a5 scheduler::TaskQueueManager::DoWork()
#16 0x7fffede922f4 _ZN4base8internal7InvokerINS_13IndexSequenceIJLm0ELm1ELm2EEEENS0_9BindStateINS0_15RunnableAdapterIMN9scheduler16TaskQueueManagerEFvNS_9TimeTicksEbEEEFvPS7_S8_bEJNS_7WeakPtrIS7_EERS8_bEEENS0_12InvokeHelperILb1EvSB_EEFvvEE3RunEPNS0_13BindStateBaseE
#17 0x7ffff7c8c879 base::debug::TaskAnnotator::RunTask()
#18 0x7ffff7cb61c5 base::MessageLoop::RunTask()
#19 0x7ffff7cb64f8 base::MessageLoop::DeferOrRunPendingTask()
#20 0x7ffff7cb6a9c base::MessageLoop::DoDelayedWork()
#21 0x7ffff7cb818d base::MessagePumpDefault::Run()
#22 0x7ffff7cb5cf1 base::MessageLoop::RunHandler()
#23 0x7ffff7ce49a0 base::RunLoop::Run()
#24 0x7ffff7cb4e00 base::MessageLoop::Run()
#25 0x7ffff5efdb72 content::RendererMain()
#26 0x7ffff6015c1e content::RunZygote()
#27 0x7ffff60164b2 content::RunNamedProcessTypeMain()
#28 0x7ffff6016f03 content::ContentMainRunnerImpl::Run()
#29 0x7ffff60157e0 content::ContentMain()
#30 0x555555a2b42b ChromeMain
#31 0x7fffeeb22ec5 __libc_start_main
#32 0x555555a2b309 <unknown>
  r8: ffff9621564676a8  r9: ffff962156467698 r10: 0000000000000008 r11: 0000000000000202
 r12: 00007fffffffaee8 r13: 00007fffffffaed8 r14: 00007fffffffad10 r15: 00007fffffffad00
  di: 0000000000000001  si: 0000000000000001  bp: 00007fffffffad00  bx: 0000000000000000
  dx: 0000000000000006  ax: 0000000000000000  cx: ffffffffffffffff  sp: 00007fffffff9e28
  ip: 00007fffeeb37cc9 efl: 0000000000000202 cgf: 656c000000000033 erf: 0000000000000000
 trp: 0000000000000001 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]



Please use labels and text to provide additional information.

 

Comment 1 by mmenke@chromium.org, May 11 2016

Cc: caseq@chromium.org
[+caseq]  Your CL was the last one I'm aware of to touch this area, though not sure how it could be the cause for this particular failure.

Comment 2 by mmenke@chromium.org, May 11 2016

So it looks like the issue here are the renderer time stamps, not the timestamps for the browser.  Somehow PendingRequestInfo::request_start is after PendingRequestInfo::response_start.  I am not seeing an obvious cause for this, however.  I'm not terribly familiar with the ResourceDispatcher's renderer-side logic, though.
Status: Archived (was: Untriaged)
Archiving P3s older than 1 year with no owner or component.

Sign in to add a comment