New issue
Advanced search Search tips

Issue 795376 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression

Blocking:
issue 776877
issue 786219



Sign in to add a comment

OpenGL error produced on Linux AMD R7 240 causing multiple tests to fail

Project Member Reported by kbr@chromium.org, Dec 15 2017

Issue description

In this build:
https://ci.chromium.org/buildbot/chromium.gpu.fyi/Linux%20Release%20%28AMD%20R7%20240%29/3654

multiple Chrome-based tests started to fail. The GPU process crashes with this assertion failure:

[29989:29989:1212/181000.701888:ERROR:gles2_cmd_decoder.cc(2586)] [.CompositorWorker-0x386ad5a7e200]GL ERROR :GL_INVALID_OPERATION : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command
[29904:29923:1212/181000.705931:WARNING:simple_synchronous_entry.cc(1170)] Could not open platform files for entry.
[29989:29989:1212/181000.719198:ERROR:gles2_cmd_decoder.cc(2586)] [.CompositorWorker-0x386ad5a7e200]GL ERROR :GL_INVALID_OPERATION : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command
[29989:29989:1212/181000.737420:FATAL:feature_info.cc(1617)] Check failed: ::gl::g_current_gl_context_tls->Get()->Api->glGetErrorFn() == static_cast<GLuint>(0x0) (1282 vs. 0)
#0 0x55b36e4b0c2c base::debug::StackTrace::StackTrace()
#1 0x55b36e4d085c logging::LogMessage::~LogMessage()
#2 0x55b36f78c47c gpu::gles2::FeatureInfo::InitializeFloatAndHalfFloatFeatures()
#3 0x55b36f786022 gpu::gles2::FeatureInfo::InitializeFeatures()
#4 0x55b36f87531d gpu::gles2::GLES2DecoderImpl::HandleGetRequestableExtensionsCHROMIUM()
#5 0x55b36f892d78 gpu::gles2::GLES2DecoderImpl::DoCommandsImpl<>()
#6 0x55b36f76ea8f gpu::CommandBufferService::Flush()
#7 0x55b36fccb4b8 gpu::CommandBufferStub::OnAsyncFlush()
...

Looking at the blame list, the most likely cause is:

GLX: implement GLSurface PresentationCallback
https://chromium-review.googlesource.com/809704

It sounds to me like those changes are causing an OpenGL error which is propagating through the system, causing later calls to fail.

penghuang@ can you please take this? Unfortunately we don't have tryservers for this configuration but you can log on to the bot. If there's an easy way to blacklist your new changes on Linux AMD that would be the most expedient way to get things back to a working state.

Thanks.

 

Comment 1 by kbr@chromium.org, Dec 15 2017

Blocking: 786219
Project Member

Comment 2 by bugdroid1@chromium.org, Dec 18 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/34841e0c1743edb739badae281b6d047f4c9412c

commit 34841e0c1743edb739badae281b6d047f4c9412c
Author: Peng Huang <penghuang@chromium.org>
Date: Mon Dec 18 22:05:09 2017

GLSurfaceGLX: try to fix Linux AMD R7 240 bot

Bug:  795376 
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Icfbe08fe64625d0aa2a6fc559a1d4f2ed0758341
Reviewed-on: https://chromium-review.googlesource.com/832912
Commit-Queue: Peng Huang <penghuang@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#524822}
[modify] https://crrev.com/34841e0c1743edb739badae281b6d047f4c9412c/ui/gl/gl_surface_glx.cc

Status: Fixed (was: Assigned)

Sign in to add a comment