Member

I originally missed these out. They're also async, so we need to chain future logs after this to ensure they're printed in the same order.

Fixes #1824.

Member Author

@devoncarew in the screenshot above, the exception text says <collected>. This seems to be what comes back from the VM when I call toString() on the exception. Is there anything we can do to avoid this? (it doesn't seem consistent, but it seems to happen almost every time).

Contributor

This seems to be what comes back from the VM when I call toString() on the exception. Is there anything we can do to avoid this? (it doesn't seem consistent, but it seems to happen almost every time).

I don't know that there's anything we can do on the client side. cc @bkonyi; something to consider - when object refs are sent to clients, we may want some brief grace period before they can be considered for collection. A ring buffer of the last n objects sent to the client? Have objects flushed from a buffer after some short duration in the buffer?