Very bad jit.buffer~ bug

I am not sure the proper channels for bug reporting, but this one was killing some of my standalones for a while.

If a standalone is created that contains a jit.buffer~ object, there MUST be a regular buffer~ object of the same name inside the patch or else it will crash badly.

For example, this will not run on my system:

Running that as a standalone gives an instant "MaxMSP must quit" error. Add a buffer~ object:

...and everything works fine.

I am on XP Pro SP2