I don't have an M1 myself. I've had two reports of 3-5 second video lag with my Vuo-made application, when running on M1 Macs. Given the performance of these machines, I can only guess something else is going on.
If I'm running a composition in a window, ie VuoCompositionLoader is running, and then I sleep my Mac, when I wake my Mac the main Vuo app has forgotten about the window, and so there's no convenient way to kill the window except for quitting VuoCompositionLoader.
Expected behaviour would be that the Stop button in the main Vuo app would still be visible, and hitting that would close/stop the current app in the VuoCompositionLoader.
●●●○ — It prevents me from completing a specific task with Vuo.
Steps causing the bug to occur:
I think I have a RAM consumption problem. Whenever I run a VUO composition with VuoLoader or exported as an Application, the use of RAM gradually increases.
In compositions that are only 2 buttons that send an OSC commands, the application starts at 29Mb and gradually grows to 4Gb of RAM after 2 days of use. But with applications with more functions after 18 hours of use, it can be using 47Gb of RAM ( using Virtual Memory ).
Do you have any advice about how to manage or which nodes I should be careful about so that there is no constant increase in RAM usage?
I am using Mojave and Vuo 2.2.0
We were able to reproduce the problem. Unfortunately, we don't see a way to modify the composition to avoid that leak, but we can hopefully have a fix in the next Vuo release. Thanks for letting us know!