Re: [chuck-users] machine.add issue

Adam Tindale wrote:

Please find the smallest example that borks in the same way so we can narrow down the bug.

I investigated, and it seems it was partly my fault. Attached are three files. To reproduce a problem similar to what I had, run "chuck --loop instruments", then do "chuck + eats_cpu.ck". Because the call to Instruments.analog.bd() is not sporked (but called) chuck will eat cpu rapidly. Why is that? Is it my mistake or is this a bug in chuck? Secondly, if I instead do "chuck --loop instruments" followed by "chuck + leaks.ck", chuck will slowly but surely eat my ram. I had a bigger example going which did this faster. After 40 minutes or so my 512 Mb of ram was digested along with my 1G swap, and the machine... well it got quite un-responsive :-) Why is that? My mistake or a chuck bug? This is with 1.2.0.6-rc3 under Linux... -- peace, love & harmony Atte http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/compositions float grid[16]; for(0=>int i; i grid[i]; } 1 => grid[0]; 0 => grid[4] => grid[12]; while (true) { for(0=>int i; i now; grid[i] => float level; if(level - std.rand2f(0,1) > .3){ Instruments.analog_bd(level); } } } public class Instruments { fun static void analog_bd(){ analog_bd(1); } fun static void analog_bd(float dynamic){ analog_bd(dynamic, 400::ms); } fun static void analog_bd(float dynamic, dur length){ .007 => float volume; sinosc s => ADSR env => dac; // envelope .1 => env.decayTime; .001 => env.attackTime; .1 => env.releaseTime; 0 => env.sustainLevel; volume * dynamic => env.gain; 160 => float freq; 0 => s.phase; 1 => env.keyOn; now + length => time note_off; while (now < note_off) { freq => s.freq; .86 *=> freq; 5::ms => now; } } } float grid[16]; for(0=>int i; i grid[i]; } 1 => grid[0]; 0 => grid[4] => grid[12]; while (true) { for(0=>int i; i now; grid[i] => float level; if(level - std.rand2f(0,1) > .3){ spork ~ Instruments.analog_bd(level); } } }