Problem still occurs on 1.3.22.36179
I finally got around to sending the logs in, forgot to do so when I initially reported this, maybe it’ll be fixed now (though I don’t know if this is actually so hard to reproduce that my logs would be essential to the solution of this)