FIXED: Kinect CHOP GPU memory leak

Kinect CHOP, Skeleton parameter. If you put any wrong expression there, it will start taking more and more GPU memory every frame.

youtu.be/0aF7kyN122U

Video demo below.
Derivative 12.04.2017 - 13.01.54.01.mp4 (27.7 MB)

Hey, thanks for the report. I think the leak is likely downstream. What nodes are the CHOP channels used in? I think the leak is likely happening in the the TOPs those CHOPs are driving. When there is no channels in the CHOPs something wrong is occurring.
Can you post your. toe file?

Don’t mind messy code, had to make it all quick
CubicKinect.toe (15.9 KB)

Thanks the bug seems to be in the text1 Text TOP node. If you make sure Counter always has valid data (use a Replace CHOP for example), then you can avoid this bug. I’ll look into fixing it.

This behavior is fixed in builds 2017.34500 or later. Thanks for the report.