-
-
Notifications
You must be signed in to change notification settings - Fork 35.4k
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
Memory leak when playing video on firefox browser #26527
Comments
There was a recent change in https://rawcdn.githack.com/mrdoob/three.js/dev/examples/webgl_video_panorama_equirectangular.html |
That change seems to have fixed it, the memory leak doesn't happen on the example from that url. |
With the upcoming release However, you can also enhance the material that uses the video texture with |
@danyjf Do you mind reporting this issue to Mozilla at https://bugzilla.mozilla.org/ ? I'm on macOS and could not reproduce the memory leak with the above examples. When testing So maybe this issue is Windows exclusive and related to the DirectX backend of Firefox. |
I was traveling when I saw this comment and only had access to my laptop, but when I tested on my laptop (which is also running windows 11 with same version of Firefox), the memory leak didn't happen. When I got back home tested again on my desktop PC and the memory leak was still happening on it. Graphics card: AMD Radeon RX 6700 XT. |
Description
When opening a three.js example from the three.js website on firefox (version 116.0) the memory usage shown on task manager keeps increasing.
Reproduction steps
Code
The code is in the three.js examples.
From my tests the leak happens when rendering a mesh with a material that uses a THREE.VideoTexture as the map parameter.
Live example
Screenshots
Screenshots from playing video on this example.
Memory before playing video:
Memory after 2 minutes of playing video:
Memory after 5 minutes of playing video:
Version
r155
Device
Desktop
Browser
Firefox
OS
Windows
The text was updated successfully, but these errors were encountered: