#166997

i can no longer reproduce this error in v1.056
Thank you 🙂