NickGeorge

So, somehow or other, when I do something very routine (nearly identical to something I do elsewhere), my mxj object is "killing" everything that it talks to. For instance, if it has an outlet wired to an number box, the box will stop responding. This is most salient if, after I kill one, I create a new one right next to it, wired to the same outlet, and watch it respond while the other stays still. If I delete-undo the "dead" number box, it starts working again. So Strange!

Now, before I go into detail about what I do (it's a bit convoluted), I was wondering if anyone had seen this before, and knew under what circumstances things like this happen.

So, somehow or other, when I do something very routine (nearly identical to something I do elsewhere), my mxj object is "killing" everything that it talks to.  For instance, if it has an outlet wired to an number box, the box will stop responding.  This is most salient if, after I kill one, I create a new one right next to it, wired to the same outlet, and watch it respond while the other stays still.  If I delete-undo the "dead" number box, it starts working again.  So Strange!

some-kind-of-kill-message

The only possibility I can see here is that your outlet generated some strange messages (or maybe a lot of messages) that froze the connected number. Have you tried stepping trough with the debugger?

Or maybe there's just something in your Max configuration? Did you have overdrive mode enabled?

Some kind of kill message