• mwebsterm

    (@mwebsterm)


    Hi, ??

    I’ve just tried to log into my admin area of my webiste and have got this error:

    Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 262144 bytes) in /home/customer/www/mooreattuned.com/public_html/wp-includes/functions.php on line 5125

    I have looked through multiple threads before posting this one and have tried increasing the memory by inserting this code in the wp-config area:
    define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
    on the line before ‘That’s all, stop editing! Happy publishing’ as advised on the wpbeginner website. I’ve increased the amnount to 384M and then 512M as advised by someone in another thread, yet the problem persists.

    Even though I get the error when I try to log in, I can visit my page and will have the WordPress toolbar the top as if I’m logged in, but then when I try to access the dashboard or anything, I get the same error, or this one:

    Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 20480 bytes) in /home/customer/www/mooreattuned.com/public_html/wp-includes/class-wp-query.php on line 593

    Is there any other things I can do? I’m not very good with code, just your average user.

    Thanks in advanced.

    • This topic was modified 2 years ago by mwebsterm.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 15 total)
  • threadi

    (@threadi)

    You could try disabling plugins to reduce the number of functions that are executed here. Without wp-admin you can remove plugins via FTP as described here: https://www.ads-software.com/support/article/faq-troubleshooting/

    Terry

    (@tbilton)

    I have exactly the same issue.
    It started yesterday morning, and though the website is active, the wp-admin/ is showing me the same error you are seeing.
    I worked with SiteGround and they told me to restore the site to the previous nights backup, which i did, and it worked again.
    Same thing happened again this morning, so i reached out to SiteGround again, and they told me to restore last nights backup again and turn off WordPress updates in the SG admin area.
    After the restore the WP version is back to 6.03 and the admin area is accessible and i have turned off WP upgrades to stop it upgrading to 6.1

    According to the research i’m supposed to look for a plugin that may be the culprit by turning off all the plugins and then upgrading to WP 6.1 and turning on each plugin individually and then test admin access each time…

    Has anyone else found a plugin that is causing this?

    threadi

    (@threadi)

    Thread Starter mwebsterm

    (@mwebsterm)

    Hi @tbilton I’m with Siteground too and they told me the same thing. So thanks for the heads up.

    @threadi thanks, I’ll try it out. Is it adviable then as Terry said to disable every plugin and then reactivate them one by one until I find the offending plugin?

    threadi

    (@threadi)

    Yes, I had already described that above.

    Thread Starter mwebsterm

    (@mwebsterm)

    I get that, I wasn’t ignoring you or anything. But as I said, treat me as a complete newbie as I’ve never had to fix a website before or anything close.

    So while you did say try disabling plugins (and I looked at the thread you linked, thank you for that btw) I wasn’t sure what method was better: to disable plugins one by one until the website works, or disable all and gradually reactivate them one by one until it crashes again.

    threadi

    (@threadi)

    You can’t give a general answer to that. If you have a lot of plugins, I would start with “big” ones. Especially those that are functionally essential for your website. If you are not aware of this, just go through alphabetically.

    Thread Starter mwebsterm

    (@mwebsterm)

    So, it doesn’t look like it’s a plugin, but the update itself. I reverted my site to the backup of a few days ago, pre WP 6.1, disabled all the plugins, then upgraded back to 6.1, then before even reactivating any plugins I refresh the page and I had the error. SO… can I stick to 6.03 until another update is made?

    Terry

    (@tbilton)

    Thanks for that update…. i’ll keep my site at 6.03 too till i hear things have improved.

    Terry

    threadi

    (@threadi)

    I have not encountered this with a single 6.1 installation so far. I would recommend that you contact your hoster’s support, as they may not be providing sufficient resources.

    Terry

    (@tbilton)

    UPDATE UPDATE UPDATE:
    I restored prod to stage, disabled all my plugins, changed my theme from BETheme to 2020 and installed 6.1 (from 6.03).
    It updated successfully.
    I changed the theme back to BETheme and it crashed again.

    I’ll open a ticket with BETheme to see if they can figure out why.

    Terry

    (@tbilton)

    UPDATING THE LAST UPDATE:

    I went to the BETheme support site and saw a posting that they released a patch upgrade 26.5.1.4 that fixed this WP 6.1 issue.

    I went into Stage, upgraded BETheme to the latest version, upgraded WP to 6.1 and BINGO… it works like a charm.

    Thread Starter mwebsterm

    (@mwebsterm)

    Yes, I use BeTheme too. I’ve downloaded the patch too, but havent upgraded to WP 6.1 yet. Thanks for letting me know!

    Thanks to both of you.

    I’m experiencing errors with betheme today, will try upgrading to latest theme tomorrow to see if it fixes my issues.

    Error Details
    =============
    An error of type E_ERROR was caused in line 564 of the file /home/XXXXX/public_html/wp-content/themes/betheme/visual-builder/classes/visual-builder-class.php. Error message: Allowed memory size of 268435456 bytes exhausted (tried to allocate 37871880 bytes)

    WordPress version 6.1.1
    Active theme: Betheme Child (Version: 26.6.2 )
    PHP version 8.1.12

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Yet another fatal error memory exhausted error’ is closed to new replies.