Johannes Regnier

The display part of a patch I'm working on makes use of several jit.gl.text3d objects. When the graphic engine is set to "glcore", it suffers from a rather massive memory leak, making the patch unusable after a couple hours running. I traced back the problem to the jit.gl.text3d objects (getting rid of them solve the issue).

Apparently this leak doesn't happen when setting the engine to "gl2".

Is there anything I should be aware when using glcore, that I maybe overlooked?

The display part of a patch I'm working on makes use of several jit.gl.text3d objects. When the graphic engine is set to "glcore", it suffers from a rather massive memory leak, making the patch unusable after a couple hours running. I traced back the problem to the  jit.gl.text3d objects (getting rid of them solve the issue).
Apparently this leak doesn't happen when setting the engine to "gl2".
Is there anything I should be aware when using glcore, that I maybe overlooked?

The display part of a patch I'm working on makes use of several jit.gl.text3d objects. 

jit-gl-text3d-memory-leak-with-glcore-graphic-engine-max-v-8-5-1

please send along the patch that exhibits the leak along with some instructions to get it running, and your system specs (About Max -> Copy support information to clipboard), and we'll check it out.

You can send to me directly if you prefer, or file an issue with support 

jit.gl.text3d memory leak with glcore graphic engine ( MAX v.8.5.1)