WordPress - get on 4.3.1 ASAP!

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

Patrick

Administrator
Staff member
Dec 21, 2010
12,511
5,792
113
STH has been really slow lately. It turns out that there was a bug in WordPress 4.3.0 that was causing a ballooning query on every page load:
Code:
{s:32:"40cd750bba9870f18aada2478b24840a";a:2:{s:8:"schedule";b:0;s:4:"args";a:0:{}}}i:1442383695;a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:2:{s:8:"schedule";b:0;s:4:"args";a:0:{}}}i:1442383696;a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:2:{s:8:"schedule";b:0;s:4:"args";a:0:{}}}i:1442383701;a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:2:{s:8:"schedule";b:0;s:4:"args";a:0:{}}}i:1442383704;a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:2:{s:8:"schedule";b:0;s:4:"args";a:0:{}}}i:1442383705;a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:2:{s:8:"schedule";b:0;s:4:"args";a:0:{}}}i:1442383710;a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:2:{s:8:"schedule";b:0;s:4:"args";a:0:{}}}i:1442383711;a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:2:{s:8:"schedule";b:0;s:4:"args";a:0:{}}}i:1442383712;a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:2:{s:8:"schedule";b:0;s:4:"args";a:0:{}}}i:1442383713;a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:2:{s:8:"schedule";b:0;s:4:"args";a:0:{}}}i:1442383728;a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:2:{s:8:"schedule";b:0;s:4:"args";a:0:{}}}i:1442383732;a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:2:{s:8:"schedule";b:0;s:4:"args";a:0:{}}}i:1442383735;a:1:
Also saw
Code:
mysql> select * from wp_options where
option_name='cron';
ERROR 2020 (HY000): Got packet bigger than 'max_allowed_packet' bytes
And a lot of
Code:
Fatal error: Allowed memory size of abc bytes exhausted (tried to allocate xyz bytes) /wp-includes/wp-db.php
Even the giant boxes running STH were feeling the weight of the what became 100MB query, on every page load. I am sure if @dba sees this he will cringe.

Just wanted to give a quick shout out to Steven @ Rack911.com ( Linux Server Management, Linux Server Security, Linux Disaster Recovery | RACK911 ) for helping figure this one out. I think within a few minutes he found others with similar issues.

It is an absolutely crippling bug even with big/ fast processors, SLC SAS SSDs and lots of RAM. The new version came out today (Sept 15, 2015) but it was too late for STH as the back-end had already became inaccessible. Thanks to the help of Rack911 this got resolved.