Skip to content

chrome_webgl2_workaround#4945

Merged
juj merged 1 commit into
emscripten-core:incomingfrom
juj:chrome_webgl2_workaround
Feb 16, 2017
Merged

chrome_webgl2_workaround#4945
juj merged 1 commit into
emscripten-core:incomingfrom
juj:chrome_webgl2_workaround

Conversation

@juj

@juj juj commented Feb 14, 2017

Copy link
Copy Markdown
Collaborator

Work around the issue that Chrome 56 and Chrome 57 shipped WebGL 2 without the new WebGL 2 function entry points. Fix a bug in glBufferData() where legacy GL emulation was used without gating for #if LEGACY_GL_EMULATION.

@juj juj added the GL label Feb 14, 2017
Comment thread src/library_gl.js
usage = 0x88E8; // GL_DYNAMIC_DRAW
break;
}
#endif

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This block was actually missing #if LEGACY_GL_EMULATION, coming from an old commit d2a3ea8.

…thout the new WebGL 2 function entry points. Fix a bug in glBufferData() where legacy GL emulation was used without gating for #if LEGACY_GL_EMULATION.
@juj juj force-pushed the chrome_webgl2_workaround branch from 8f26dc5 to cab6be0 Compare February 14, 2017 12:38

@erunehtar erunehtar left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified, the error goes away in Chrome 56.

@kripken

kripken commented Feb 14, 2017

Copy link
Copy Markdown
Member

Overall lgtm, but do we not expect chrome to fix this soon? (if soon, then maybe best to just wait?)

@erunehtar

Copy link
Copy Markdown

@kripken without this fix we can't upgrade Emscripten otherwise it breaks running in Chrome release today.

@kripken

kripken commented Feb 14, 2017

Copy link
Copy Markdown
Member

I see, ok.

@juj

juj commented Feb 16, 2017

Copy link
Copy Markdown
Collaborator Author

Overall lgtm, but do we not expect chrome to fix this soon? (if soon, then maybe best to just wait?)

They said they will have the fix in Chrome 58, and they're asking to land this workaround in the meanwhile and not wait. So I'll go ahead and push this in.

Thanks @gouletr for testing!

@juj juj merged commit 42ffd7a into emscripten-core:incoming Feb 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants