Memory leak when using preFX in the same scene as a 3.8 Spine object

[Bambosh]

Version

• Phaser Version: 3.80.1

• Operating system: Windows

• Browser: All browsers

Description

If you assign preFX to any gameObject in a scene that also contains a 3.8 spine object, something goes wacky in the renderer and starts spewing the same instructions into this.renderer.glAttribLocationWrappers on repeat.
Game performance eventually tanks, as renderer.glAttribLocationWrappers.indexOf() is run multiple times per render cycle.

Example Test Code

Click the text to trigger the bug
https://codepen.io/Bambosh/pen/KKjKdxP

Additional Information

[greptile-apps]

For internal use only

To address the memory leak issue in Phaser 3.80.1, please check the following updates and fixes:

1. DynamicTexture: Ensure setSize(width, height) is called for both WebGL and Canvas. This prevents width and height from being set to -1 in Canvas mode.

   DynamicTexture.setSize(width, height);

2. DynamicTexture: Check if the glTexture bound to the current frame is stale and destroy it before binding the one from the Render Target to prevent memory leaks.

   if (this.glTextureIsStale) {
       this.destroyGLTexture();
       this.bindRenderTargetTexture();
   }

Refer to the changelog for version 3.80.1 for more details on these fixes.

References

/changelog/3.80.1/CHANGELOG-v3.80.1.md
/changelog/3.80/CHANGELOG-v3.80.md

About Greptile

This response provides a starting point for your research, not a precise solution.

Help us improve! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

Ask Greptile · Edit Issue Bot Settings

[Scross086]

I see this with later versions of spine as well. If you use preFX and spine in the same scene, a significant memory leak begins. I'm using spine 4.1 I think