To reproduce, throttle the connection (in Chrome "Regular 2G" seems to reliably reproduce this). It can even happen in brand new grains, so the bug must be happening completely client side.
I'm not sure what the cause is, but it's obviously some sort of timing issue.