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

Issue 602679 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug

Blocking:
issue 587781



Sign in to add a comment

WebGL2 deqp/gles3/functional/shaderbuiltinvar.html freezes Chromium's rendering on Linux

Project Member Reported by cwallez@chromium.org, Apr 12 2016

Issue description

When running the deqp/gles3/functional/shaderbuiltinvar.html test with --enable-unsafe-es3-apis, Chrome's rendering freezes at some point. Chrome itself isn't frozen since copy pasting from it works, as does scrolling.

This can be reproduced either on Chrome stable or top of tree Chrome

At the same time the following shows up in the console:
[29442:29442:0412/130731:ERROR:gles2_cmd_decoder.cc(8014)] [.CommandBufferContext.Offscreen-MainThread-0x2dafbc18eb40]PERFORMANCE WARNING: Attribute 0 is disabled. This has significant performance penalty
[29442:29442:0412/130731:ERROR:gles2_cmd_decoder.cc(8014)] [.CommandBufferContext.Offscreen-MainThread-0x2dafbc18eb40]PERFORMANCE WARNING: Attribute 0 is disabled. This has significant performance penalty
[29442:29442:0412/130731:ERROR:gles2_cmd_decoder.cc(8014)] [.CommandBufferContext.Offscreen-MainThread-0x2dafbc18eb40]PERFORMANCE WARNING: Attribute 0 is disabled. This has significant performance penalty
[29442:29442:0412/130731:ERROR:gles2_cmd_decoder.cc(14362)] [.CommandBufferContext.RenderCompositor-0x2dafbbf908c0]GL ERROR :GL_INVALID_OPERATION : glTexStorage2DEXT: <- error from previous GL command
[29442:29442:0412/130731:ERROR:gles2_cmd_decoder.cc(2167)] [.CommandBufferContext.RenderWorker-0x2dafbbf90500]GL ERROR :GL_INVALID_OPERATION : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command
[29442:29442:0412/130731:ERROR:gles2_cmd_decoder.cc(2167)] [.CommandBufferContext.RenderWorker-0x2dafbbf90500]GL ERROR :GL_INVALID_OPERATION : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command
[29442:29442:0412/130731:ERROR:gles2_cmd_decoder.cc(2167)] [.CommandBufferContext.RenderWorker-0x2dafbbf90500]GL ERROR :GL_INVALID_OPERATION : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command
[29442:29442:0412/130731:ERROR:gles2_cmd_decoder.cc(2167)] [.CommandBufferContext.RenderWorker-0x2dafbbf90500]GL ERROR :GL_INVALID_OPERATION : GLES2DecoderImpl::DoBindTexImage2DCHROMIUM: <- error from previous GL command

With the glTexStorage2DEXT and DoBindTexImage2DCHROMIUM lines being repeated a lot.
 

Comment 1 by kbr@chromium.org, Apr 14 2016

It's important that this be tracked down and fixed. Client code should not be able to break the browser's rendering in this way.

Corentin, how does this behave with --use-gl=angle? If it fixes the problem, that makes switching to ANGLE on Linux even more urgent. I suspect it'll fix it since ANGLE does a better job virtualizing GL contexts than Chrome's command buffer.

The problem doesn't reproduce with --use-gl=angle. This makes ANGLE even more important to ship on Linux indeed :)
I can confirm these work:
  google-chrome --disable-gpu
  google-chrome --use-gl=angle
Last one did output ERROR in console, see near end of attachement.

This doesnt work: (black screen)
  google-chrome

New Ubuntu 16.04 (with VB guest additions installed and 3D acceleration enabled) in VirtualBox 5.1.6 on Windows 10 host (Dell Precision Tower 3620 with NVIDIA NVS 315 gpu)
virtualbox5.1.6 ubuntu16.04 googlechrome53.0.2785.116 gpu error.txt
42.1 KB View Download
The ERROR you get with --use-gl=angle is because ANGLE isn't shipped on Linux yet, if you want to test this you'll need to compile Chromium from sources. I'll see if this problem still repros on ToT Chromium.
Owner: cwallez@chromium.org
Status: Available (was: Untriaged)
Tested again, it is fixed. It was probably caused by missing support in the ANGLE shader translator.

barrystaes@gmail.com: Can you be more precise? What exactly are you running when doing google-chrome and what web page are you opening? 
Ok thanks that would explain the angle error i got. I have no requirement for that so i'll let it be, although trying to compile Chromium from source is tempting.. :)

I just tested this and want to point out: DISABLING 3D acceleration for VirtualBox guest makes the issue disappear: chrome renders OK. See versions/specs details in my previous post. VM also used VT-x/AMD-V, Nested Paging, KVM Paravirtualization.

cwallez@chromium.org: When doing google-chrome i was running the latest Ubuntu 16.04 LTS. Nothing more than a clean install, doing `sudo apt-get update && sudo apt-get upgrade` and downloading `google-chrome-stable_current_amd64.deb` from google.com/chrome
Status: Fixed (was: Available)
It seems that the problem you have is an entirely different issue, can you open a new one? Also it might be worth trying Canary to see if it was fixed in ToT (thinking of https://bugs.chromium.org/p/chromium/issues/detail?id=613722 ).

Closing this issue as fixed.

Comment 8 by kbr@chromium.org, Oct 5 2016

Also, barrystaes@: feel free to email me the ID of the new bug you file. Please include the contents of about:gpu in all configurations.

Ok opened new issue https://bugs.chromium.org/p/chromium/issues/detail?id=658668
Sorry for the delay.

cwallez@chromium.org: FYI i cant download a Google Canary for Linux to test ToT, and cant read that issue. (permissions)

Sign in to add a comment