janslupski

This is the exact error message in the apache2 log file (although I’m not sure if it is helpful, as it does not point what exactly exhausted the memory):

[Fri Dec 18 16:54:25.293026 2020] [proxy_fcgi:error] [pid 9348:tid 140635919070976] [client xxxxxxxxxxxxxxxxxx] AH01071: Got error 'PHP message: PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /[xxx]/wp-includes/wp-db.php on line 1972\nPHP message: PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 73728 bytes) in /[xxx]/wp-includes/functions.php on line 4212\n'
[Fri Dec 18 16:54:25.293083 2020] [proxy_fcgi:error] [pid 9348:tid 140635919070976] [client xxxxxxxxxxxxxxxxxx] AH01071: Got error 'PHP message: PHP Fatal error:  Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0\n'

@wwday3 do you operate on a large database? Since it seems not to be that common issue I wonder what could be additional (non-typical) factor involved…

(My WordPress has ~20K posts and database dump is ~1GiB)

rev 2154675 from SVN works, rev 2168173 does not
From the comments this is change that happened between 3.5.1 & 3.6.0

Ah, and error occurs at https://…/wp-admin/edit.php (maybe other pages too).

hth

• This reply was modified 3 years, 11 months ago by janslupski.

So I’m the second one.
I see that problem after upgrade from 3.4.1 to 3.7.6.

If I disable auto-post-thumbnail – no more “memory exhausted error”.
If I revert to 3.4.1 – no more “memory exhausted error”.

Will try to figure out at which version it has started.