This bug turned really nasty, resulting in database connection failures.
I think this is strongly related to this issue, as we had a huge list of cronjobs: https://core.trac.ww.wp.xz.cn/ticket/33423
Check in phpmyadmin if the table wp_options is a decent size (< 1mb) and if not try to clear the option named ‘cron’.
I’ve manually edited taxonomy.php l4448 to correctly create the cronjobs, now waiting for update 4.3.1 to fix this.
I experience exactly the same issue (memory exhausted) since the upgrade, although we have a memory limit of 128M, what should be enough.
Doing a quick search I find a large number of websites with the same error.
Do you have suggestions how to find the specific function which causes the error? (other than line 384 in wp-includes/functions.php)
The error fortunately only shows up in the backend, every call to admin-ajax.php results in a 500 error.
