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

Issue 606354 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Chrome crashes on failed DCHECK in mash.

Project Member Reported by kylec...@chromium.org, Apr 25 2016

Issue description

When running mash in the Oxygen or Pixel configuration there is an occasional failed DCHECK that crashes the mus process. It happens infrequently and I'm not sure if any specific actions trigger it.

[131383:131383:0425/092627:838083214704:FATAL:gl_renderer.cc(1156)] Check failed: tex_scale_x <= 1.0f (1.04281 vs. 1)
#0 0x7f1348bf7bbe base::debug::StackTrace::StackTrace()
#1 0x7f1348c14c9a logging::LogMessage::~LogMessage()
#2 0x7f1345dffcc4 cc::GLRenderer::DrawRenderPassQuad()
#3 0x7f1345dfdb58 cc::GLRenderer::DoDrawQuad()
#4 0x7f1345df4093 cc::DirectRenderer::DrawRenderPass()
#5 0x7f1345df3319 cc::DirectRenderer::DrawRenderPassAndExecuteCopyRequests()
#6 0x7f1345df3100 cc::DirectRenderer::DrawFrame()
#7 0x7f1345cc2bcb cc::Display::DrawAndSwap()
#8 0x7f1345cc52f7 cc::DisplayScheduler::DrawAndSwap()
#9 0x7f1345cc45bd cc::DisplayScheduler::OnBeginFrameDeadline()
#10 0x7f1345cc69ec _ZN4base8internal7InvokerINS_13IndexSequenceIJLm0EEEENS0_9BindStateINS0_15RunnableAdapterIMN2cc16DisplaySchedulerEFvvEEEFvPS7_EJNS_7WeakPtrIS7_EEEEENS0_12InvokeHelperILb1EvSA_EEFvvEE3RunEPNS0_13BindStateBaseE
#11 0x7f1345cc69ec _ZN4base8internal7InvokerINS_13IndexSequenceIJLm0EEEENS0_9BindStateINS0_15RunnableAdapterIMN2cc16DisplaySchedulerEFvvEEEFvPS7_EJNS_7WeakPtrIS7_EEEEENS0_12InvokeHelperILb1EvSA_EEFvvEE3RunEPNS0_13BindStateBaseE
#12 0x7f1348bf8c26 base::debug::TaskAnnotator::RunTask()
#13 0x7f1348c1e9e5 base::MessageLoop::RunTask()
#14 0x7f1348c1ed18 base::MessageLoop::DeferOrRunPendingTask()
#15 0x7f1348c1ef2b base::MessageLoop::DoWork()
#16 0x7f1348c21929 base::MessagePumpLibevent::Run()
#17 0x7f1348c1e581 base::MessageLoop::RunHandler()
#18 0x7f1348c496cd base::RunLoop::Run()
#19 0x7f13466742ef shell::ApplicationRunner::Run()
#20 0x7f13466744ac shell::ApplicationRunner::Run()
#21 0x7f1346671078 MojoMain
#22 0x000000449e08 shell::RunNativeApplication()
#23 0x000000446dce shell::(anonymous namespace)::RunNativeLibrary()
#24 0x000000447093 _ZN4base8internal15RunnableAdapterIPFvPvN4mojo16InterfaceRequestIN5shell5mojom11ShellClientEEEEE3RunIJRKS2_S8_EEEvDpOT_
#25 0x00000044705c _ZN4base8internal7InvokerINS_13IndexSequenceIJLm0EEEENS0_9BindStateINS0_15RunnableAdapterIPFvPvN4mojo16InterfaceRequestIN5shell5mojom11ShellClientEEEEEESD_JRS6_EEENS0_12InvokeHelperILb0EvSF_EEFvSC_EE3RunEPNS0_13BindStateBaseEOSC_
#26 0x00000044929f shell::ChildProcessMain()
#27 0x000000446cf5 shell::ChildProcessMain()
#28 0x00000040d530 shell::StandaloneShellMain()
#29 0x7f1347f26ec5 __libc_start_main
#30 0x000000409090 <unknown>

It seems possibly related to this TODO: https://code.google.com/p/chromium/codesearch#chromium/src/components/mus/ws/platform_display.cc&sq=package:chromium&type=cs&l=115
 
Components: MUS>Phase>1

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

Has this been fixed by one of Rob's changes?
Status: WontFix (was: Untriaged)
I had poster circle running on device for 4 days. I'd claim that this bug is fixed.
I don't have a device with me now but I should have included I saw this bug on http://www.cbc.ca/news/ and often while elements on the page was moving during the initial loading. I can test if that still occurs on device when I have access again.
Components: Internals>Services>WindowService
Components: -MUS>Phase>1

Sign in to add a comment