Since the problem occurs for a regular rule, too, it seems like this is caused by a bug in Mail and not anything that SpamSieve is doing.
Is the rule moving messages to a server mailbox on another account (i.e. not the problem Gmail account)? If so, please try changing it to use a Spam mailbox on the same Gmail account, as the bug may only manifest when moving messages between accounts.