-
-
Notifications
You must be signed in to change notification settings - Fork 35.3k
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
potential leak while disposing WebGLRenderer #8987
Comments
Sounds good. Would you like to do a Pull Request? |
Sure ! |
olivierchatry
pushed a commit
to olivierchatry/three.js
that referenced
this issue
May 25, 2016
olivierchatry
pushed a commit
to olivierchatry/three.js
that referenced
this issue
May 26, 2016
mrdoob
pushed a commit
that referenced
this issue
May 27, 2016
This PR should solve the issue: #13122
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the problem
Hello,
My software is switch between two renderer (threejs / own SVG renderer ), removing the gl context while swapping renderer. While profiling for leaks, I noticed that two arrays in Three WebGLRenderer are not cleared when I call dispose on the context, namely opaquesObject and transparentsObject.
https://github.com/mrdoob/three.js/blob/master/src/renderers/WebGLRenderer.js#L27
My workaround is to render an empty scene, so that they get cleared by the rendering, but it would be better if "dispose" actually clear them.
Hope I am clear enough, but if you need more information, do not hesitate
Three.js version
Browser
OS
Hardware Requirements (graphics card, VR Device, ...)
The text was updated successfully, but these errors were encountered: