Fatal error: Out of memory

Hi,

That error is usually correct. On the Diagnostics page, run a memory test. Does it pass? Also, search for memory on the Diagnostics page. What are the settings listed?

Thanks!
Brian

I have a similar error:

Fatal error: Out of memory (allocated 190054400) (tried to allocate 23424505 bytes) in /nfs/c07/h02/mnt/111184/domains/rskservice.com/html/wp-includes/wp-db.php on line 1262

Here is the memory test result:

Wordfence Memory benchmarking utility version 6.1.7.
This utility tests if your WordPress host respects the maximum memory configured
in their php.ini file, or if they are using other methods to limit your access to memory.

–Starting test–
Current maximum memory configured in php.ini: 256M
Current memory usage: 53.00M
Setting max memory to 90M.
Starting memory benchmark. Seeing an error after this line is not unusual. Read the error carefully
to determine how much memory your host allows. We have requested 90 megabytes.
Completing test after benchmarking up to 80.25 megabytes.
–Test complete.–

Congratulations, your web host allows you to use at least 80.25 megabytes of memory for each PHP process hosting your WordPress site.

WFBrian, please help me to fix it!

I’m getting exactly the same and it’s ever since wordfence has updated on around 15 of my websites. Any help on this would be great?

Wordfence Memory benchmarking utility version 6.1.7.
This utility tests if your WordPress host respects the maximum memory configured
in their php.ini file, or if they are using other methods to limit your access to memory.

–Starting test–
Current maximum memory configured in php.ini: 256M
Current memory usage: 67.25M
Setting max memory to 90M.
Starting memory benchmark. Seeing an error after this line is not unusual. Read the error carefully
to determine how much memory your host allows. We have requested 90 megabytes.
Completing test after benchmarking up to 80.50 megabytes.
–Test complete.–

Congratulations, your web host allows you to use at least 80.50 megabytes of memory for each PHP process hosting your WordPress site.

Hello mcnaden and tunder,
Version 6.1.8 is now available and it includes this fix: “Change wfConfig::set_ser to split large objects into multiple queries”. We are hoping that this fix will sort out most issues with the prepare function in wp-db (wp-db.php lines 1246-1266in WordPress 4.5). The fix does require the PHP extension MySQLi. You can check if MySQLi is enabled on your site via the “Click to view your system’s configuration in a new window” on Wordfence Diagnostics page. Just click that link and see if you find “MySQLi” on the list. If your host has disabled php_info, please contact your host to find out if you have the extension MySQLi.

Please update to the latest version of Wordfence and let us know how you’re doing after that!

Hi wfasa,

I’m having a similar problem, but my out of mmeory issue occurs on line 1307 of wp-db.php. WordPress 4.7.3 currently, running on PHP 5.3.24,with Wordfence 6.3.4. MySQLi is also enabled (Client API library version 5.0.77, Client API header Version 5.0.95).

Happy to provide additional details if needed.

Thanks in advance!

Sorry, I should probably have provided the actual error message… ;]

Fatal error: Out of memory (allocated 123994112) (tried to allocate 19974733 bytes) in /home/content/h/e/r/herbcso/html/blog/wp-includes/wp-db.php on line 1307

Sorry for the dribs-and drabs posting here, but I just keep thinking of new information that might be useful.

This seems to have been happening since December without me noticing it, actually – I’m basing that on that fact that Wordfence is telling me that the last successful scan was on December 9.

Is there an option to enable Wordfence to email me if a scan failed? (I looked but I might have missed it)

Also, I’ve enabled low resource scanning, no change with that.

I also tried excluding this file, but either I’m specifying it wrong (possible), or it’s forcing a scan because this is a core WP file…?