Had that happen as well. While I saw it a few times with an earlier beta, 1.0.173 seems to have (re-?)introduced a bug here.