Hi,

I recollect something similar with fluidsynth opcodes -  I think they don't free the allocated memory of the soundfont (when you run in CsoundQt or other host). This is not probably not problem if you run in command line. Would you care to do some tests and issue a bug report?

tarmo

On Aug 27 2019, at 6:52 pm, Syl Morrison <honoonu@gmail.com> wrote:
It's me again sorry for being too active here lol,
I'm running into an issue I wonder if anyone could shed some light on using ctcsound with the FluidSynth opcodes,
Basically on the first few runs it works smoothly, but on around the 5th it's giving me "error out of memory" when trying to load the soundfont. So what I'm getting from that is that the memory allocated to loading the soundfonts isn't being cleared when the program is terminated, I was wondering if there's something I'm missing I need to do in the destructor for my csound thread to free up all used memory when the program is quit? 
I'm on Manjaro linux, i5, 8gb ram if that's relevant at all, and am using 64bit python which doesn't have a cap at 2gb ram
Cheers!
Syl
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