It has only recently been reported, but it probably started with an upgrade to 3.9.6. It also looks like a minor version upgrade to 3.9.7 has corrected the issue.
Thank-you for replying to the initial query.
Thank-you for replying to the initial query.