There are so many things it could be, it would be quite time consuming to get it down to a barebones test. I think it might be the hack mentioned in this thread that caused it; using a forced collision message to update the visuals. After I removed the hack the issue hasn’t happened again.
Edit: Now it did happen again. I may need to look closer at this one after all.