This fails (with large probability, as issue is not 100% deterministic) on 0.5.0, catching the bug in this version.