Insta/hard crash

[rodrigo.constanzo]

@tremblap

I think no resizing at all would be the best. Rod, what don’t you have one large buffer, with 1 variable (many ways to do that, for instance [v]) which is the valid end point? that way you never resize, which is my favourite best practice for Max buffer in RT settings (since I had so many problems with them over the years)

I need fades in places, and need to channel fuse/manage, so I have to go into HIRT land and back, so I need to resize at some point along the way.

If I could @fadein/@fadeout in fluid.bufcompose~ then I wouldn’t need to do any of that.

Onto to the main crash-ness, after some more hangs this morning @a.harker was able to narrow down the problem to multithreading with fluid.bufcompose~ being… “potentially dangerous”.

So this part of the patch:

Needed to be turned into this:

It seems like there were two distinct problems going on, what appears to be a M4L-related crash crash, and a fluid.bufcompose~-threading-related hang hang.