memory leak in Avenue when changing layer size

[Piotrus04]

Hi, there is a memory leak in Avenue when i scrub the layer video dimension by hand.

Os x 11.3.1
Avenue 7.5.0 77960

Steps to reproduce :
- new composition
- put a solid color and play this clip
- change / scrub the video width or height.
- monitor the memory used by avenue in Activity Monitor

the memory used by Avenue will raise without limit

all the best
pierre

[Arvol]

Does this happen in 7.6.1?

[Zoltán]

How about the latest Big Sur update? Maybe that also fixes stuff?

[Piotrus04]

No, it doesn't solve the issue.
But as we don't change all time the layer dimension, i guess nobody discovered this issue.
I tracked it because firstly in another more complex project, i was coding a ffgl plugin using FBOs to store the previously rendered frame, and had many issues of memory leak when both the clip is played and also the preview. This cause an issue i couldn't figure out why the memory leak appeared also.
of course, this topic is about the memory leak without my plugin, just using resolume standard solid color.

if anybody has an example source code of fbo use (over time), i am VERY interested ))

[Zoltán]

Changing the layer dimension works just fine for me, no memory increase there with the solid Color Source, in 7.6.1
Are you sure your plugin is not loaded as a layer blend or effect?
Is there something else we'd need to add to the picture?

Which mac are you using?

[Piotrus04]

Here is a link to demonstrate.

https://filetransfer.io/data-package/euBNJArK#link

i am using macbook pro m1 2020

and of course, it is not important issue, because we don't change the layer size as this in normal condition, but i just wanted to notice it to your team.

as i am also struggling with fbo use on the previously said plugin,
i don't know if this is a common issue between the fbo use, and other things regarding the m1 processor.

i published an example code in the ffgl github repos, in the issue section. Really sorry for the inconvenience
if i am doing something bad in the code ...

https://github.com/resolume/ffgl/issues/73

[Zoltán]

M1 macs are still running Resolume via Rosetta, so hard to say what's going on in the translation.
I've tried the same on an M1 mac mini, and there 7.6.1 didn't increase memory usage for me either above 1.6GB.

Does the Memory usage go back after a minute or two for you?
Do you have any outputs enabled or NDI/Syphon?

[Piotrus04]

Yes you are right, the memory usage goes down after a while, around 2 minutes.
and yes, syphon and ndi disabled.
we can close this topic.

If you have any fbo (over time) example code, i will really appreciate, because the simple action to declare a ScopedFBOBinding, and bind its texture to a shader makes the memory usage grow very fast.
"fbo example", a must have in the ffgl repos ! ))

[Zoltán]

Ok, looks like memory management then cleaning up.

I've read there are other memory issues with BigSur on M1 https://www.macworld.com/article/549755 ... g-sur.html

[Piotrus04]

thank you