Support » Plugin: Jetpack by WordPress.com » 4.3.1 memory error

  • With Jetpack 4.3 I just got a blank page when trying to access the settings. With the latest patch to 4.3.1 I now get the following error instead:

    Fatal error: Allowed memory size of 100663296 bytes exhausted (tried to allocate 71 bytes) in ******/public_html/wp-includes/wp-db.php on line 2409

    I added the stars to remove sensitive information. Help?

Viewing 8 replies - 1 through 8 (of 8 total)
  • I’m seeing similar issues with 4.3.1. I can’t access the Settings page in Jetpack. It’s a blank screen.

    [09-Sep-2016 02:57:51 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72 bytes) in /wp-includes/wp-db.php on line 2399
    [09-Sep-2016 02:58:26 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 72 bytes) in /wp-includes/meta.php on line 838

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    I’m afraid that’s a common WordPress issue. Could you try to follow the instructions here to solve the problem?
    https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

    We’re also working on some memory improvements in Jetpack, to make the plugin a lighter in the next release!

    Let me know how it goes.

    We went through the instructions above but still running into the same issue. Any ETA on the next update?

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    @rmspangler If you aren’t allowed to increase memory allocated to PHP on your site, could you contact us via this form, and mention this thread? We can help you install the development version of Jetpack, and see if that helps you.

    I meant to come back and lost track of time. My server is already configured with a PHP memory limit of 256M, a time limit of 300 and a WordPress Memory Limit of 512M. It’s a solid state server with 32GB of RAM, which rarely gives me problems like this.

    I do have 7500 blogs running on this subdomain network. Is it possible that JP is trying to run through an update of sorts and is failing? If I put the site in Development mode I can get to the settings panel, but regular mode results in those errors, and a white screen.

    Not sure if that helps at all. Thanks @jeherve.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    I do have 7500 blogs running on this subdomain network. Is it possible that JP is trying to run through an update of sorts and is failing?

    That could indeed be it, but we’ve run tests on much larger Multisite networks before the release, and didn’t run into issues. The problem might be related to a conflict between Jetpack and one of the plugins you use on that network, though. Do you use plugins that may save a really big amount of data as post meta on your posts? If so, could you let me know which ones?

    It might also be worth updating to the latest Beta version of Jetpack, available here, as we’ve made more changes to the Jetpack sycnhronization process in the past few weeks.

    Thanks!

    cnmo

    (@cnmo)

    I had the same issue when activating JetPack, but do not currently have the website on
    a local server because I do not own it (have only been given administrative permission to edit it) and am pretty new to wordpress. How do I fix this? I am unable to access settings or anything because I am directed immediately to a blank page that says : “Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 49152 bytes) in /home/XXX/public_html/wp-admin/includes/user.php on line 95”, and I could not figure out how to connect this site to Binami when I tried to connect to a local host to edit.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    @cnmo You can follow the instructions here to solve the issue:
    https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

    If you can’t access those settings, you’ll need to contact your hosting provider for help.

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