Thanks, it took some effort to reproduce this issue since it very rarely happens here. This should be fixed in the next version.