Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebGL context restored incorrectly (pixi v5) #5700

Closed
YuryKuvetski opened this issue May 20, 2019 · 3 comments · Fixed by #5872
Closed

WebGL context restored incorrectly (pixi v5) #5700

YuryKuvetski opened this issue May 20, 2019 · 3 comments · Fixed by #5872
Labels
🕷 Bug Verified that it’s actually a legit bug that exists in the current release.

Comments

@YuryKuvetski
Copy link
Contributor

Everything works fine for pixi v4, but in v5 (WebGL 2) application restored incorrectly

Expected Behavior

For both versions of pixi, application should be restored correctly.

Current Behavior

If you choose v5 pixi version with webgl2, application is not restored.
If you choose v4 pixi version with webgl, application restored fine.

Steps to Reproduce

  1. Open https://pixijs.io/examples/#/demos-basic/container.js on PC Chrome
  2. Choose v5 pixi version
  3. Open chrome dev tools console with iframe context
  4. Write next command to lose webgl context document.querySelector('canvas').getContext('webgl2').getExtension('WEBGL_lose_context').loseContext()
  5. Wait for a few sec
  6. Write next command to restore webgl context document.querySelector('canvas').getContext('webgl2').getExtension('WEBGL_lose_context').restoreContext()

Environment

  • pixi.js version: 5.0.3
  • Browser & Version: Chrome 74.0.3729.157
  • OS & Version: MacOS Mojave 10.14.4
@ivanpopelyshev
Copy link
Collaborator

Its a known issue. I've fixed geometries but not texures and shaders :) How critical is that for you, is it something that you can integrate into app a month after now or do you need it this week?

@ivanpopelyshev ivanpopelyshev added the 🕷 Bug Verified that it’s actually a legit bug that exists in the current release. label May 20, 2019
@YuryKuvetski
Copy link
Contributor Author

Good. I think it's ok for us to wait a month.

@JetLua
Copy link
Contributor

JetLua commented Jun 24, 2019

@ivanpopelyshev Are you already doing this? If not, I can add a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕷 Bug Verified that it’s actually a legit bug that exists in the current release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants