We've fixed at least two different bugs that have caused this problem since posting to HN. Please let us know if you're still seeing it. It's been a hard one to reproduce!