This occurred when recording with allocations. Nothing seemed to be affected as far as I can tell, but this was dumped a few times during recording.

This is just a warning to let you know it happened. We can only store so much, and we figured that dumping a warning was better than silently losing data.

That makes sense -- should atleast change the message to be less scary, as this seems like an unintentional uncaught exception, rather than a warning. Bonus points eventually if we can display something in the allocations view, or during recording, saying "hey we're losing allocations", like how we have buffer full messages

I'm not worried about this.