Context Navigation

Changes between Initial Version and Version 1 of Ticket #17462, comment 7

initial	v1
2	2	> As well as the longer time out period we could, as part of the loop in wp-cron.php, check the difference in time since the start and if it's approaching the lock time out then break. That means that processes that have taken too long stop as if they have died though I suppose they would clear the lock in doing so.
3	3
4		Poked a hole in this one. First long running process may clear the transient from under a second process which has followed on after $flag has timed out. This would allow a third cron process to run without being blocked (and, possibly, so on) leading to the current problem. Haven't tested to confirm, but seems like it's possible.
	4	Poked a hole in this one if applied alone. First long running process may clear the transient from under a second process which has followed on after $flag has timed out. This would allow a third cron process to run without being blocked (and, possibly, so on) leading to the current problem. Haven't tested to confirm, but seems like it's possible. However, it's a good complement to Ryan's patch.
	5
	6	Edit to clarify.