Fatal error after recent update.

  • cjblythe

    (@cjblythe)


    11 years, 6 months ago

    I recently updated the Wordfence plugin and discovered it did not reactivate after. I get the fatal error:
    Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 58082527 bytes) in /home/emptynes/public_html/wp-includes/wp-db.php on line 1040.

    I checked the line in the file mentioned and don’t see any way to increase memory size.

    Can anyone help me with this?

    If not, can I possibly reinstall an older version that worked?

    https://wordpress.org/plugins/wordfence/

Viewing 3 replies - 1 through 3 (of 3 total)
  • WFSupport

    (@wfsupport)

    11 years, 6 months ago

    Which file? The php.ini?

    tim

    Thread Starter cjblythe

    (@cjblythe)

    11 years, 6 months ago

    I’m not sure what you mean, but the file noted in the error is “/home/emptynes/public_html/wp-includes/wp-db.php.”

    I have no idea otherwise.

    WFSupport

    (@wfsupport)

    11 years, 6 months ago

    Ahh. I got you. I was confused by which file you were referencing that you checked.

    This is an indication that your memory in php.ini is not set high enough. You can define this in your php.ini file (usually found in /etc on linux systems check your documentation for windows servers). Look through the file for a line like this:
    memory_limit = 128M
    Keep in mind the 128M is probably different. That’s the amount of memory that php is allowed to consume. If you have 10 plugins and combined they consume more memory than you have allocated, you’re going to have problems. You can assign more by increasing this value. (my personal sites have 256M allowed, but this is for a pretty big site with a substantial number of hits and plugins). Make sure and restart httpd (apache) after making changes here. There is also an option on the options page of our plugin that allows you to set how much memory WF can use (mine is set to 256 here as well).

    tim

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Fatal error after recent update.’ is closed to new replies.