Ge;<br><br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Heh, ChucK is certiainly good at generating new sorts of issues!</blockquote>
<div><br><br>Indeed and cheerfully so.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>(Are you sure we can't blame ChucK?)
</blockquote><div><br><br>Well, that computer will have issues over nearly anything and needs a reboot or two a day. It needs a re-install, I'll probably set her up with Ubuntu.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
To make sure I have facts straight:<br>this is running command line chuck (or miniAudicle) on XP?</blockquote><div><br>Well, both. The Mini has the added advantage of slowly increasing it's shred counter before bailing.
<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I postulate this may be the unfinished garbage collector catching up with<br>
us. What type of things are happening in these thousands of shreds? New<br>unit generators allocated? String concatenation? new objects?</blockquote><div><br>None of those. The only thing those shreds have that would alocate memory is their arguments and the results of calculations being send to ugen members. I was quite carefull there but I might've made a mistake somwhere. It started crashing before I could sort out matters like functionality...
<br><br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Kilo-shreds, and even mega/giga/(probably not tera yet)-shreds should be
<br>well within the normal chuckian operational range, assuming they don't do<br>things that compell ChucK to leak loads of memory.</blockquote><div><br><br>Right. That's what I thought.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
(In the end, I am<br>fairly certain it *is* ChucK's fault) Can you post a perhaps simplified<br>version of the kilo-shred that is causing this disaster?</blockquote><div><br>Yeah, I'll try to nail it down tomorow.
<br><br>To be sure; this initial test *was* ineficient and I was expecting trouble but this was a bit much.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
By the way, we are making progress on garbage collection though nothing is<br>enabled in the release. We'll definite priority boost GC. To sort<br>of quote Samuel L. Jackson: I have had it with this muthachucking garbage
<br>in this muthachucking language!</blockquote><div><br>I'm fairly sure garbage collection won't help in this particular case. I'm generating two shreds per samp right now so that's a lot of shreds at any given time even before there is a chance for anything to become garbage. I'll try to nail down a simplified yet issue-causing version.
<br> </div><br>Thanks,<br>Kas.<br></div>