Last modified: 2007-04-07 10:56:32 UTC
There seems to be something filling the job queue in a loop, we see in pretty quick succession: 5723 5726 3 (sometimes) 2 5723 ... etc. If this is caused by possibly recursive behaviour in template calls, it was likely introduced - or stirred into the job queue - with changes made during the recent days, i.e. most likely on or after April, 4th., when I altered inside a system of interdependent templates which I mostly did not write or design, and at best partially understand. I tried to simplify them using parser functions now instead of highly complicated other contition-evaluating templates of the pre-parser- function era. I remember, I had inspected the job queue after such a change and saw it go down to zero, but frankly cannot recall when.
*** This bug has been marked as a duplicate of 9518 ***