New issue
Advanced search Search tips

Issue 624221 link

Starred by 1 user
Status: WontFix
Merged: issue 624256
Owner:
pdr@chromium.org
Closed: Jul 2016
Cc:
piman@chromium.org
erikc...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer

Project Member Reported by pdr@chromium.org, Jun 29 2016 
Version: tip-of-tree at 80a042718b7407f95e9461222f6b840eb9b4ca73
OS: OSX 10.11.5 / non-retina monitor

What steps will reproduce the problem?
(1) Launch Chromium
(2) Notice console errors:
[27148:1295:0628/180146:ERROR:gles2_cmd_decoder.cc(10681)] [.DisplayCompositor-0x7fd8f208ae00]GL ERROR :GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer
[27148:1295:0628/180146:ERROR:gles2_cmd_decoder.cc(10681)] [.DisplayCompositor-0x7fd8f208ae00]GL ERROR :GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer
[27148:1295:0628/180146:ERROR:gles2_cmd_decoder.cc(10681)] [.DisplayCompositor-0x7fd8f208ae00]GL ERROR :GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer
[27148:1295:0628/180146:ERROR:gles2_cmd_decoder.cc(10681)] [.DisplayCompositor-0x7fd8f208ae00]GL ERROR :GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer
[27148:1295:0628/180146:ERROR:gles2_cmd_decoder.cc(10681)] [.DisplayCompositor-0x7fd8f208ae00]GL ERROR :GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer
[27148:1295:0628/180146:ERROR:gles2_cmd_decoder.cc(10681)] [.DisplayCompositor-0x7fd8f208ae00]GL ERROR :GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer
[27148:1295:0628/180146:ERROR:gles2_cmd_decoder.cc(10681)] [.DisplayCompositor-0x7fd8f208ae00]GL ERROR :GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer
[27148:1295:0628/180146:ERROR:gles2_cmd_decoder.cc(10681)] [.DisplayCompositor-0x7fd8f208ae00]GL ERROR :GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer
[27148:1295:0628/180146:ERROR:gles2_cmd_decoder.cc(10681)] [.DisplayCompositor-0x7fd8f208ae00]GL ERROR :GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer
[27148:1295:0628/180146:ERROR:gles2_cmd_decoder.cc(10681)] [.DisplayCompositor-0x7fd8f208ae00]GL ERROR :GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer
[27148:1295:0628/180146:ERROR:gles2_cmd_decoder.cc(10681)] [.DisplayCompositor-0x7fd8f208ae00]GL ERROR :GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer
[27148:1295:0628/180146:ERROR:gles2_cmd_decoder.cc(10681)] [.DisplayCompositor-0x7fd8f208ae00]GL ERROR :GL_INVALID_OPERATION : glScheduleCALayerCHROMIUM: failed to schedule CALayer

I think this may be due to the recent changes in gles2_cmd_decoder.cc. ErikChen, can you take a look?

Comment 1 by pdr@chromium.org, Jun 29 2016

Cc: erikc...@chromium.org
Owner: piman@chromium.org
Looks like erikchen went OOO for the rest of the week.

@piman, can you take a look? I didn't manually check this one, but it could be related to  https://crbug.com/624256 .

Comment 2 by piman@chromium.org, Jun 30 2016

Mergedinto: 624256
Status: Duplicate (was: Assigned)

Comment 3 by pdr@chromium.org, Jul 1 2016

Status: Available (was: Duplicate)
 issue 624256  was fixed but this is still present :(

De-duping

Comment 4 by erikc...@chromium.org, Jul 4 2016

Status: Assigned (was: Available)

Comment 5 by piman@chromium.org, Jul 6 2016

Cc: -erikc...@chromium.org piman@chromium.org
Owner: erikc...@chromium.org
Erik, can you take a look? I only originally took this to fix things while you were OOO, but I'm not well equipped to debug this.

Comment 6 by erikc...@chromium.org, Jul 6 2016 

Looking into it.

Comment 7 by erikc...@chromium.org, Jul 6 2016 

I can't reproduce off of top of tree b1320e8f04eb906f295def43d4cf4894d7bc5b7a. Tried on two different devices.

Can you reproduce this with a clean profile? I'm guessing that there's something showing up in your NTP thumbnails that is triggering this? [Either that or something has changed between 4 days from now and today.]

Comment 8 by pdr@chromium.org, Jul 6 2016

Cc: erikc...@chromium.org
Owner: pdr@chromium.org
I won't be back to my mac until tomorrow. I'll assign this to myself to verify / close / reassign.

Comment 9 by pdr@chromium.org, Jul 8 2016

Status: WontFix (was: Assigned)
Looks like this has been fixed. In comment 5, I may have caught the tree between when the regression was re-introduced and when it was re-fixed.
►

Sign in to add a comment