Fixed in Vuo version:
- OS X 10.10
Steps causing the bug to occur:
- Send OSC values from VDMX to VUO
- Interpret Values
- Create moving layers with OSC data.
- Memory is consumed at an alarming rate.
How did the result differ from what you expected?:
The longer the composition runs the more the memory is consumed.
When did you first notice this bug?:
Have you found a workaround?:
No workaround. I recreated the Vuo composition in Isadora and no such memory leak was apparent so I'm confident the bug is with VUO not VDMX.