Segment out of order on an ADT msg caused process to PANIC

received a message with a segment out of order that was different from the definition in the variant.  The engine appeared to get hung up that message and continued to try to process that message as if in an infinite loop until the process eventually PANIC’d.  I would have expected the engine to error the message out.  Has anyone experienced this before?  Did the engine act properly on this message?