It doesn't seem like a very complex patch (attached). The numbers from 3 LFOs are converted into XYZ structure w/ Javascript, then queued to draw a 2D Path with a Sprite. When I replace the JS with Kineme Struct Maker the leak stops, so it must be the JS.
Is Quartz Composer writing to virtual memory?
Has anyone else seen QC w/ JS have this behavior of eating up Disk Space while running?
On a second note, is this the correct method for creating a structure in JS to make a point? I'm pretty new to JS in QC so I thought maybe I'm doing something wrong. Or is it the 2D Path Object placing temp images on the HD?
- Code: Select all
function (__structure output) main (__number input[3])
{
var result = new Object();
var output = new Array();
result.output = [input[0],input[1],input[2]];
return result;
}
This is on a Early 2011 Macbook Pro, 2.2GHz i7, 8GB RAM, AMD Radeon HD 6750M 1024 MB VRAM, OS X Lion 10.7.1, Xcode 4.1, KinemeCore.