Steve Robinson - 2018-05-26

Forgot to mention I experienced this issue with version 1.6.34.