This had been already reported as an issue and we’ve identified a prime candidate why this happens in the first place. You can check this thread:
This is already fixed in master branch and will be deployed in 5.10.0. We are also working on another feature to improve it even further. We plan on releasing 5.10.0 ASAP.