Fatal Error: Why Is This Occurring?

  • Unknown's avatar
    jtpedersen · Member ·

    Hello,

    I installed Jetpack a few days ago. Working fine; very happy.

    This afternoon, any attempt to access a Page on my site (Log In, Receive by Mail, About…etc.) returns the following error message:

    “Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 261900 bytes) in /home/jtpeders/public_html/blog/wp-includes/post.php on line 99”

    If I deactivate Jetpack, all error conditions go away. If I reactivate it, the error condition returns. Repeated numerous times across different browsers, consistent behavior.

    Not sure what to do about this. Guidance would be appreciated.

    Thank you,

    JT…
    Blog url: http://jtpedersen.net

  • Unknown's avatar
    jtpedersen · Member ·

    I’ve been after this awhile…though the timing of my response might suggest otherwise.

    I have since discovered that the behavior appears to be tied to having -both- Jetpack and the LinkedIn Share Button plugin active at the same time.

    Disabling -either- Jetpack or LinkedIn Share Button plugins will eliminate the Fatal error condition described previously. As soon as both are activated simultaneously the error condition reappears.

  • staff-blorbo · Staff ·

    It looks like your hosting provider is severely limiting your available memory.

    Here are three ways to increase PHP’s memory allocation:

    1. If you can edit or override the system php.ini file, increase the memory limit. For example, memory_limit = 256M

    2. If you cannot edit or override the system php.ini file, add php_value memory_limit 256M to your .htaccess file.

    3. If neither of these work, it’s time to ask your hosting provider to temporarily increase PHP’s memory allocation on your account. Keep in mind that most decent hosting providers allocate 32 MB to PHP under each account, and most decent hosting providers allow users to temporarily increase the memory allocation. If your hosting provider won’t accommodate you, perhaps it’s time to find a new hosting provider.

  • Unknown's avatar
    jtpedersen · Member ·

    Hello macmanx,

    Thank you for you comments. I’ll admit, something along the lines of what you describe, is what initially came to mind for me.

    However (reaffirming just now), the problem is as I posted in my second response. Having both Jetpack active -and- the LinkedIn Share Button immediately triggers the fatal error. Disabling either plugin eliminates the issue.

    I have since added a custom LinkedIn service to Sharedaddy and obviated the need for LinkedIn’s own button.

    While my own immediate problem is now resolved, this coding failure represents a problem that should be understood.

    Cheers,
    JT…

  • staff-blorbo · Staff ·

    Well, it’s not really a coding issue necessarily. The root of the problem is that the two plugins active simultaneously uses more memory than your hosting provider offers on your account, which is quite stingy.

    For example, I have no issue running both plugin simultaneously on my own self-hosted blog.

    Did you have any luck with bumping your memory allocation?

  • The topic ‘Fatal Error: Why Is This Occurring?’ is closed to new replies.