Rob;<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
The short statement is &quot;I can&#39;t optimize what I can&#39;t see&quot;.  It would be nice to have visibility into where the storage is getting eaten up.  Or a GC.<br>
<br>
</blockquote><div><br>I agree. I think you might be able to tell something about memory allocation by turning up the &quot;verbose&quot; setting to something very high but we do need GC as well. I could also imagine that eventually the Audicle and/ or mini might have such diagnostic tools added to them.<br>
<br>It&#39;s not clear to me why you are discarding those two shreds after you used them though. Why not simply have two shreds that wait for eventA / eventB respectively, signal eventC when their respective event comes in and afterwards resume waiting? That would merge two events into one and would only require your time-out function to be stopped or rest in case the event arrives before the timer times out.<br>
<br>Yours,<br>Kas.<br></div></div><br>