Make WordPress Core

Opened 15 years ago

Closed 10 years ago

#11826 closed defect (bug) (worksforme)

Endless Cron Spawn

Reported by: hakre's profile hakre Owned by: westi's profile westi
Milestone: Priority: normal
Severity: normal Version: 2.9
Component: Cron API Keywords:
Focuses: Cc:


I somehow get it managed to keep such request in memory while they consume CPU all the time. I noticed that first a week ago or so and now I was able to find out some specifics:

REQUEST_URI /wordpress-trunk/wp-cron.php?doing_wp_cron

Maybe there is a condition for an endless loop in there?

Change History (7)

#1 @hakre
15 years ago

  • Version set to 2.9

#2 @dd32
15 years ago

  • Component changed from General to Cron
  • Milestone changed from Unassigned to Future Release
  • Owner set to westi

The cron file ignores user aborts, and sets a time limit of unlimited.

What cron tasks did you have queued? Without knowing which task it is, its a bit hard to track it down.

#3 @hakre
15 years ago

Good question, I could not finish my tests on that one right now.

#4 @azizur
14 years ago

  • Cc azizur added

I am getting some what related error:

Warning: fopen(http://dev.wordpress/wp-cron.php?doing_wp_cron): failed to open stream: Connection timed out in /var/www/dev.wordpress/wp-includes/class-http.php on line 1063 

#5 @scribu
14 years ago

azizur: for that error see #11831

#6 @chriscct7
10 years ago

  • Keywords close dev-feedback added

Recommend close based on non-reproducible problem that without reporter feedback on cron jobs, would be impossible to track down. Likely not a WordPress core bug.

#7 @johnbillion
10 years ago

  • Keywords close dev-feedback removed
  • Milestone Future Release deleted
  • Resolution set to worksforme
  • Status changed from new to closed

No feedback in four years.

Note: See TracTickets for help on using tickets.