I got the same amp values.  I think the issue is that you are using
random values from amp.  If you use "seed 0" in instr 0, you'll get
different amps, some audible, some not.  You might try adjusting your
iAmp1 and iAmp2 lines to not go between -60 db and 0 db, which is a
pretty wide range. (I tried with 3 instead of 60 and it was fine).

I did not get any malloc assertion errors here on Windows.

On Tue, Sep 26, 2017 at 3:12 PM, Hlöðver Sigurðsson  wrote:
> Evening csounders,
>
> I'm struggling to find out what's causing the amps from the opcode I made
> from Iain's Shredulator to be close to 0 after the first score event
> https://pastebin.com/raw/nBsTvs43
>
> I tried adding init 0 to all the a-rates variables, still same, leaning
> toward some memory leak as this acrually crashes csound-api for Node
> (Nwhetsell's package).
>
> B  0.000 ..  3.000 T  3.000 TT  3.000 M:  0.30066  0.24804
> B  3.000 ..  6.000 T  6.000 TT  6.000 M:  0.00128  0.00228
> B  6.000 ..  8.000 T  8.000 TT  8.000 M:  0.00041  0.00026
>
> Best,
> Hlöðver
>
> ps I'm running the newest develop branch
> pss. this is the error I get from running in the nodejs csound-api (of
> course unrelated topic to this list)
>
> malloc.c:2369: sysmalloc: Assertion `(old_top == initial_top (av) &&
> old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse
> (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here