That version didn't entirely fix the issue, so it still happens on some configurations. A hot fix is in the works and will be deployed in version 5.8.7.
FYI A wild 5.8.6.101 release has just appeared. Unsure if it fixes the bug you mentioned, the changelog hasn't been published yet and @Matt pointed out it would be 5.8.7.