wp_reschedule_event peggs CPU when very old timestamp is passed in as argument
|Reported by:||natethelen||Owned by:||anonymous|
Somehow a wp-cron timestamp got create/set with a very old timestamp of 1070. I am sure there is a bug elsewhere that caused this but now that it has happened, WordPress does not recover very gracefully. The result is that when wp_reschedule_event is called, the CPU pegs as it tries to increment it by the $interval until eventually it times out. This causes wp-crop to fail from then on. A possible solution is to set it to time() + $interval instead of incrementing. Or only increment if $timestamp < time() - (2 * $interval).
Change History (4)
- Keywords has-patch tested added; wp-cron wp_reschedule_event removed
- Milestone changed from Unassigned to 2.8