thank you for these reports. We believe this issue is fixed on our next release. Version 10.5.2. I will reply here once it's released to check if the issue continues. In the meantime, I've implemented a workaround that should fix this for your now. @davisouzarj Let us know if the issue continues. Thanks!