Issue metadata
Sign in to add a comment
|
[.PPAPIContext]GL ERROR :GL_INVALID_OPERATION : glBlitFramebufferCHROMIUM: destination framebuffer is multisampled
Reported by
r...@rossis.red,
Jun 16 2016
|
||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2768.0 Safari/537.36
Steps to reproduce the problem:
msaa_ = glGetFramebufferMultisampleInterfacePPAPI();
blit_ = glGetFramebufferBlitInterfacePPAPI();
...
glBindFramebuffer(GL_DRAW_FRAMEBUFFER_EXT, 0);
glBindFramebuffer(GL_READ_FRAMEBUFFER_EXT, msaaFramebuffer_);
blit_->BlitFramebufferEXT(context_.pp_resource(),
0, 0, widthInt_, heightInt_, 0, 0, widthInt_, heightInt_,
GL_COLOR_BUFFER_BIT, GL_NEAREST);
What is the expected behavior?
renders
What went wrong?
[.PPAPIContext]GL ERROR :GL_INVALID_OPERATION : glBlitFramebufferCHROMIUM: destination framebuffer is multisampled
Did this work before? Yes Chrome 42
Chrome version: 53.0.2768.0 Channel: canary
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 22.0 r0
This is an important regression for users of Pepper graphics who desire MSAA across mac, linux, and windows. the MSAA attributes of the pp::Graphics3d don't work on mac (see the bug about dropped frames), but this lower level API did work up until now.
,
Jun 16 2016
,
Jun 19 2016
This issue is for the Pepper Graphics API, not Flash. The error message would indicate that perhaps the default framebuffer has changed to now be multisampled and that the glBlitFramebufferCHROMIUM function can not handle that for some reason. However, I don't see other evidence that the default framebuffer is multisampled so the error message might be misleading. Either way, it is a regression.
,
Jun 20 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by r...@rossis.red
, Jun 16 2016whoops, in the regression field I meant to write Chrome 52 (not 42). i.e. this worked up until this past week. Also, here's the code for the MSAA framebuffer creation, for enlightenment: ``` glGenFramebuffers(1, &msaaFramebuffer_); glBindFramebuffer(GL_FRAMEBUFFER, msaaFramebuffer_); glGenRenderbuffers(1, &msaaColorRenderbuffer_); glBindRenderbuffer(GL_RENDERBUFFER, msaaColorRenderbuffer_); msaa_->RenderbufferStorageMultisampleEXT(context_.pp_resource(), GL_RENDERBUFFER, 4, GL_RGB8_OES, widthInt_, heightInt_); // In Chrome 52 on OSX we get GL_INVALID_OPERATION even though // everything works, so we just swallow that error here. GLenum error = glGetError(); if (error != GL_NO_ERROR) { LOG("RenderbufferStorageMultisampleEXT error: %d", error); } glFramebufferRenderbuffer(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0, GL_RENDERBUFFER, msaaColorRenderbuffer_); glGenRenderbuffers(1, &msaaDepthRenderbuffer_); glBindRenderbuffer(GL_RENDERBUFFER, msaaDepthRenderbuffer_); msaa_->RenderbufferStorageMultisampleEXT(context_.pp_resource(), GL_RENDERBUFFER, 4, GL_DEPTH_COMPONENT16, widthInt_, heightInt_); glFramebufferRenderbuffer(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, GL_RENDERBUFFER, msaaDepthRenderbuffer_); ```