• Resolved M

    (@infolegal)


    After 6.3.8. update, the scans have began failing again (and I was so happy it was working before…)
    Fatal error: Allowed memory size of 419430400 bytes exhausted (tried to allocate 65655345 bytes) in /home/…/public_html/wp-content/plugins/wordfence/lib/wfConfig.php on line 493

    Plus, the scan time is always exceeded. Initially, before the 6.3.9. update the memory issue didn’t even appear in the logs, now it does.

    How can i fix this, without allocating even more memory?

    Thanks

Viewing 11 replies - 1 through 11 (of 11 total)
  • Hi @infolegal
    Please go to (Wordfence > Tools => Diagnostics) and scroll down the page till “Send Report by Email” and send the report to “alaa [at] wordfence [dot] com”, make sure to include your forum username, I will take a look at this report and let you know my findings.

    Also, it would be helpful if you can share with me what you have selected in “Scans to Include” option.

    Thanks.

    Thread Starter M

    (@infolegal)

    Thanks a lot for your feedback. Report already sent via email. The Options set in scan will follow shortly.

    Hi Sandra,
    Thanks for sending the diagnostics report, after checking the “WP_MEMORY_LIMIT” value there, I found it set to 40MB, please increase the amount of memory allocated to PHP in WordPress to 256MB and re-check this issue.

    Let me know how it goes,
    Thanks.

    Thread Starter M

    (@infolegal)

    Hi,

    thanks for your reply. Didn’t go well. I got the host to change the WP limit (couldn’t confirm it though on my own..) then I went back and started a scan. It stopped with the same error:

    Allowed memory size of 419430400 bytes exhausted (tried to allocate 66424769 bytes) in /home/***/public_html/wp-content/plugins/wordfence/lib/wfConfig.php on line 493

    And then I tried to convert bytes to MB to see what’s wrong. And 419430400 is actually 400MB which is way beyond the 256M recommended memory. And scan was also trying to allocate another 60MB (or so).

    Any suggestions are welcomed.

    Many thanks

    Please set “How much memory should Wordfence request when scanning ” to 256 then retry running a new scan.

    Thanks.

    Thread Starter M

    (@infolegal)

    I did that and the error was:
    [May 26 11:47:08] Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 42141171 bytes) in /home/***/public_html/wp-content/plugins/wordfence/lib/wfConfig.php on line 493

    Thread Starter M

    (@infolegal)

    I have re-checked with the webhost and they set the memory limit to the correct value on the server. Even so, I still get the error on scan:

    [May 27 06:38:36] Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 43178820 bytes) in /home/***/public_html/wp-content/plugins/wordfence/lib/wfConfig.php on line 493

    That’s a little bit strange, please try to disable other activated plugins -temporarily- and run a new scan, also, I would appreciate if you can resend the diagnostics report and the memory test result to the same email address again after adjusting the memory limit configuration.

    Thanks.

    Thread Starter M

    (@infolegal)

    Not very easy to do this. I’m experiencing the issue on a production site, not a test one. I will try and let you know. Thanks

    Thread Starter M

    (@infolegal)

    I’ve upgrade to latest version and noticed the low resources scan so I gave it a try. Still same error. I also noticed and fixed the litespeed setting. I keep seeing the wp_memory_limit set to 40MB in the diagnostic page. It would be helpful to tell me where you get that value from, so I can better explain it to the hosting service support. In the wp-config the value is set to 128, and in the scan error it shows it uses 256MB.

    Thank you

    It detects the “WP_MEMORY_LIMIT” constant value set in wp-config.php file, if you are sure you have set it to a different value by adding a similar line to that file :
    define( 'WP_MEMORY_LIMIT', '128MB' );
    but the diagnostics page still reports it as 40M, then you should contact your hosting provider regarding this issue, there are so many different plugins that can check the same constant value, just in case you want to make sure about it.

    Thanks.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘memory issues’ is closed to new replies.