wp_reschedule_event peggs CPU when very old timestamp is passed in as argument

[natethelen]

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).

[natethelen]

Here is the change I made which cleaned up the problem. I replaced:

while ( $timestamp < time() + 1 )

$timestamp += $interval;

with:

$now = time();

if($timestamp >= $now)

$timestamp = $now + $interval;

else

$timestamp = $now + ($interval - (($now - $timestamp) % $interval));

This keeps the $timestamp in line with the difference from time() just like incrementing does, but without having to loop

[ryan]

(In [10969]) Fix handling of old timestamps in wp_reschedule_event(). Props natethelen. fixes #9318