<div dir="ltr">Great, thanks Bill! I figured there would be cool s7 features I didn't know I didn't know about.. :-)<div><br></div><div>Sure, checking out the article would be cool too!</div><div>iain</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, Mar 16, 2026 at 12:50 PM <<a href="mailto:bil@ccrma.stanford.edu">bil@ccrma.stanford.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On the memory leak question, there are several increasingly<br>
verbose tools: (*s7* 'memory-usage), then the heap analysis<br>
functions like s7_heap_analyze (in s7.c, all on the<br>
s7_Debugging switch), and valgrind --leak-check=full, see s7.c line <br>
103062 under s7_free. Be resigned to infinite data<br>
and endless blind alleys. (The internal s7 heap analysis<br>
stuff is currently undocumented).<br>
<br>
The 1989 article was probably the program notes for<br>
"Leviathan" published with the Wergo CD "Computer<br>
Music Currents 3". I have it as a text file if<br>
you're interested.<br>
<br>
</blockquote></div>