• Resolved fatimajesus

    (@fatimajesus)


    Hello
    Today wordfence used much more memory on scanning than usual. instead of the 36 and 76 peak of memory , used 144 and peak 173. Anyone can tell me why this happens or what it means? I ask because never happened before and I didn’t make any changes on the blog. Thanks

Viewing 9 replies - 1 through 9 (of 9 total)
  • Sharani

    (@sharani)

    Yesterday and today I am getting a similar issue that hangs up my scan – it says
    [Dec 01 09:09:46] Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 50703451 bytes) in /home/content/73/11014273/html/wp-includes/wp-db.php on line 1301

    any thoughts on how to fix this?

    Sharani

    (@sharani)

    I increased the memory to 300 and it finally ran. Now just to figure out what it means that bots are trying to log into the site almost once a minute from around the globe even though the scan didn’t show any problems.

    bobsled

    (@bobsled)

    I tried up to 400mb and still can’t get the scan to run. Still the same error. Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 9283765 bytes) I’ve also tried with deactivating all plugins, so it points to a definite Wordfence problem.

    Sharani

    (@sharani)

    they just issued a wordfence plugin update earlier today – did you install that yet? maybe that will help?

    JLY

    (@jose-luis-yanez)

    Hi there, same problem here, Allowed memory size exhausted…and it remains after latest WF update a minute ago.

    Some of the tech guys a WF suggested in the past that this might be due to PHP version at your host. Mine is 5.4.45. Please check what is yours and share it here. I would like to see if there is a pattern here related to PHP version in Hosting provider.

    Regards,

    JLY

    (@jose-luis-yanez)

    Thread Starter fatimajesus

    (@fatimajesus)

    I would like to say that today things returned to normal again and wordfence is using the normal memory to scan, or even a bit less: 25 to 54 (peak). I don’t know what happened, and know no causes for the issue.

    JLY – Completely different error/notification than the one you are pointing reference to.

    Wordfence used 27.64MB of memory for scan. Server peak memory usage was: 62.98MB

    This has to be the worst plugin update I’ve seen in a while. I get that its free “don’t look a gift horse in the mouth”, but wow.

    Plugin Author WFMattR

    (@wfmattr)

    Hi all,

    A few days ago, we fixed a server-side issue that caused some of the data that is used during scans to be larger, which could cause the memory usage issues on some sites. It should be back to normal for all sites now, so if anyone does still have an issue running out of memory during scans, please make a new post using the form at the bottom of the Wordfence forum here with the specific message you’re seeing on your site. Thanks!

    -Matt R

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘increase of memory on scanning’ is closed to new replies.