The stack trace:
[0124/101525.672283:FATAL:scoped_refptr.h(208)] Check failed: ptr_.
#0 0x7f6a0c578b9d base::debug::StackTrace::StackTrace()
#1 0x7f6a0c576fdc base::debug::StackTrace::StackTrace()
#2 0x7f6a0c5fdf2a logging::LogMessage::~LogMessage()
#3 0x7f6a0af683f2 scoped_refptr<>::operator->()
#4 0x7f6a0af923c5 base::internal::CallbackBase::polymorphic_invoke()
#5 0x7f6a0af92010 _ZNKR4base17RepeatingCallbackIFvRKN3gfx20PresentationFeedbackEEE3RunES4_
#6 0x7f6a0af93f2a gl::GLSurfacePresentationHelper::CheckPendingFrames()
#7 0x7f6a0af93977 gl::GLSurfacePresentationHelper::PostSwapBuffers()
#8 0x7f6a0afcacf8 gl::NativeViewGLSurfaceEGL::SwapBuffers()
#9 0x0000005b1675 vr::GlRenderer::RenderFrame()
Bisecting shows that this is the CL that introduced the behavior
https://chromium-review.googlesource.com/c/chromium/src/+/870851
It looks like the issue is a missing nullity check when issuing the frame callbacks.
Comment 1 by bugdroid1@chromium.org
, Jan 24 2018