High CPU Load After Update to v4.3

How could i run it on a site wich is online? It spawns processes and server crashes?

The instructions I gave work fine. Just follow them exactly.

If i put the script online on a live site then for every visitor the script will be started, right?

@vangelis183 For the minute or so that you leave it there, yes. Again, you only need the script to run one time. You put it there, visit the site, then remove the script. Simple.

Also, leaving it there won’t cause any issues. It checks to see if there are any entries to remove, and if not, then it doesn’t do anything. That’s what the if ( isset( $cron_array['wp_batch_split_terms'] ) ) { line is for.

We’ve implemented this is our MU-plugin (so we can roll it out with a mass deploy).

add_filter( 'schedule_event', 'schedule_event_unset_batch_split_terms' );
function schedule_event_unset_batch_split_terms( $event ) {
	if ( $event->timestamp == 'wp_batch_split_terms' ) {
		return false;
	}

	return $event;
}

But its really sad that this is a known issue for 5 days (and closed 3 days ago). For a developer this bug is really annoying. For a non-technical type this could just break their site.

Is there a reason that there has not been a release yet? This could break alot of sites.

fix does not work, edit taxonomy.php but every second new cronjobs are added https://take.ms/nL8kC

how can I stop it?

@otto42 Hi Samuel
I run the fix but there are just too many cron jobs scheduled. It runs forever. Is there anyway to safely clear/reset wp_batch_split_terms ?

I restored the cron field from prior wp 4.3 update with a

UPDATE wp_options SET option_value = ‘<insert old values here’ WHERE option_id = <insert option_id that holds the cron values>

My site is back to normal performance now

I run the fix but there are just too many cron jobs scheduled. It runs forever.

this problem exists here as well

You need to clean up all the cron jobs that “the fix” created.

The best way is to get the value from the cron field in wp_options from prior the upgrade.

It had inserted more than 5000 rows in my cron field, and that cost a lot of performance

@gordan43dom and @rené

This is not what i did but you could try to delete the contents of the cron row in wp_options

I dont know if this is a possible solution. But you could try. Just backup your DB in any case before you try.

@vangelis183 I thought about that , but there are just too much unknown stuff that can happen.

@vangelis183 I thought about that , but there are just too much unknown stuff that can happen.

That’s why you should use a backup.

I use backup-buddy, and there it’s in cleartext per row.

It took me 10 seconds to write the sql and get back to normal.

I made a hotfix plugin that stops WordPress from spamming the cron option:

https://github.com/phh/wp43-stahp-spamming-my-cron

I made a hotfix plugin that stops WordPress from spamming the cron option:

https://github.com/phh/wp43-stahp-spamming-my-cron

Hi Patrick.

1. Where would you put it. In mu-plugin or in an ordinary plugin.

2. Since I’ve allready fixed the taxonomy.php and cleaned up my DB, do I need it?