• Resolved myroxie

    (@myroxie)


    This fatal error keeps showing up in the admin area:
    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 820473 bytes) in /home/accountname/public_html/domainname.com/wp-content/plugins/wordfence/lib/wfConfig.php on line 445

    I have posted this to my host and they insist my account has ample memory. It is a reseller account with a decent allotment. What does this mean? And does it mean that Wordfence is no longer working for this site? I have Wordfence installed in several other sites in this same hosting account with the same resource allotment and none of them are showing this error.

    https://www.ads-software.com/plugins/wordfence/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Wordfence Security

    (@mmaunder)

    Hi there,

    Your server is running out of memory at around 64 megs. You can use the memory testing tool at the bottom of the Wordfence options page to verify this. Please ask your host to increase your memory to around 128 megs.

    Regards,

    Mark.

    Thread Starter myroxie

    (@myroxie)

    Thank you, Mark, My host tech support explicitly told me that there is 128 megs available.

    When I did the test this is what came up:
    Wordfence Memory benchmarking utility version 3.8.8.
    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: 128M
    Current memory usage: 10.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.

    @myroxie

    Did you ever get this sorted? I seem to be running in to the same issue.

    Thread Starter myroxie

    (@myroxie)

    Hello petiknz,
    I’m sorry, but I have no memory about what happened next. I haven’t run into the error lately, so I assume either I did something (that I can’t recall) or the issue self-corrected. I did move some of my sites to a new host, so that might have improved matters. But I can’t remember which site was having the problem and whether that was one that I moved. Sorry I can’t be more helpful

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal error’ is closed to new replies.