Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Core: changing refresh_interval to non-positive (0, -1, etc.) value might cause 100% CPU spin #8085
As reported on the user's list:
It looks like there is a concurrency bug when you dynamically update refresh_interval down to a value <= 0. We cancel the scheduled future when this happens, but if the future was already executing (which we don't try to cancel because we pass false to the cancel call), EngineRefresher.run will then forever continue rescheduling itself for the immediate future.