[Brian]

Fix for this is still incoming, but we shipped 1.0.2 without it. We figured folks would want the crash fixes in that release as soon as possible.

We don't have a solid repro case for this bug yet, but they have managed to observe it a couple of times and are working on a fix based on what they've seen happen.

(If anyone does come up with a way to reliably/predictably reproduce the problem, emailing the steps to trigger the bug to the support ninjas would help them test their theories/fixes.)