2024 chuckathon findings

[gewang]

further investigations needed:

1. chuck SubInstance shred is still running after SubInstance is destroyed; note: audio is disconnected but otherwise shred is still executing in the VM; possible approach each SubInstance tracks shred ID to remove when it is destroyed
2. global dac replacements UGens need more cleanup: disconnect from blackhole; possible removal or recycle for future use

[nshaheed]

have a set of available replacements dac ugens?

• while the unique dac is in use it's not in the set
• when the subinstance is destroyed, put the ugen in the set
• on subinstance creation try to take from the set, if it's empty, create a new unique ugen

I don't think this needs to be a set - it could just be a stack

Are subinstance construction/destruction multithreaded? In that case we would need some data structure with atomic find/add/remove