• Resolved mpmorris

    (@mpmorris)


    Running out of memory when trying to edit posts. Disabling WPSSO solves the problem. I’ve increased memory allocation to 256MB in php.ini. It always fails at about 53MB, though. I also tried increasing WP memory in wp-config. WPSSO is currently disabled so editors can edit their posts.

    Theme: GeneratePress
    Other plugins: AIO SEO, Jetpack, Simple CSS, Mailchimp for WordPress, WP Spamshield, Google Analytics, Oasis Workflow.

    Site: blog.apaonline.org

    https://wordpress.org/plugins/wpsso/

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author JS Morisset

    (@jsmoriss)

    WPSSO doesn’t use much memory — it sounds like it’s triggering an existing problem on your site though… Could it be image related? An old Image Magick library maybe? Try the following http://wpsso.com/codex/plugins/wpsso/faq/how-can-i-fix-an-http-error-when-uploading-images/ and let me know if that fixes the problem.

    js.

    Plugin Author JS Morisset

    (@jsmoriss)

    You could also try enabling WP_DEBUG and see if PHP / WP are reporting any errors: http://wpsso.com/codex/plugins/wpsso/installation/debugging-and-problem-solving/

    js.

    Thread Starter mpmorris

    (@mpmorris)

    First of all, thank you so much for taking the time to consider my question and respond. The errors all look like this, though the particular file on which WP drops the error varies.

    Fatal error: Out of memory (allocated 52166656) (tried to allocate 196608 bytes) in /home1/y3b6g3b1/public_html/blog/wp-admin/edit-form-advanced.php on line 418

    I’m guessing it’s some sort of plugin or plugin/theme conflict somewhere. I just don’t know exactly what the problem is.

    Plugin Author JS Morisset

    (@jsmoriss)

    Have you tried my suggestions? Have you tried GD instead of ImageMagick? Have you enabled WP_DEBUG? What errors did you find in WP’s debug.log file?

    js.

    Thread Starter mpmorris

    (@mpmorris)

    We don’t use ImageMagick. I don’t know what GD is. The errors are all as I described above.

    Plugin Author JS Morisset

    (@jsmoriss)

    If you’re not willing to use the information I provided, then there’s not much more I can do… If at a later date you change your mind, you can try the GD library (http://wpsso.com/codex/plugins/wpsso/faq/how-can-i-fix-an-http-error-when-uploading-images/) and enable WP_DEBUG (http://wpsso.com/codex/plugins/wpsso/installation/debugging-and-problem-solving/) to provide additional information leading up to the out of memory error.

    js.

    Thread Starter mpmorris

    (@mpmorris)

    I’m sorry. I don’t understand what you mean when you say that I’m not willing to use the information you provided. AS far as I can tell, you haven’t actually provided any information.

    • This has nothing to do with ImageMagick or GD (whatever that stands for). We don’t use either of those things.
    • I do not have an error when uploading images.
    • I turned on debug and I provided the error information provided by WordPress. Here it is again, for your convenience: Fatal error: Out of memory (allocated 52166656) (tried to allocate 196608 bytes) in /home1/y3b6g3b1/public_html/blog/wp-admin/edit-form-advanced.php on line 418

    What information did you provide that I’m not willing to use? I’ve done everything you’ve asked, as much as it is possible to do so.

    You don’t have to help, of course. It’s up to you.

    Plugin Author JS Morisset

    (@jsmoriss)

    You may not use ImageMagick, but WordPress does. Let me know if using GD fixes the issue.

    The out of memory error does not look like a debug.log entry. This is the only message in your debug.log after enabling WP_DEBUG?

    js.

    Thread Starter mpmorris

    (@mpmorris)

    Thank you for your patience.

    Result of adding that code to functions.php:
    Fatal error: Call to undefined function add_filter() in /home1/y3b6g3b1/public_html/blog/wp-includes/functions.php on line 12

    I also tried at the end of the file. Same result.

    I had turned on debug, but I had not enabled the debug log. It looks pretty much the same, though. I assure you that this is from debug.log:
    [11-May-2016 20:25:30 UTC] PHP Fatal error: Out of memory (allocated 52166656) (tried to allocate 196608 bytes) in /home1/y3b6g3b1/public_html/blog/wp-admin/edit-form-advanced.php on line 418

    Plugin Author JS Morisset

    (@jsmoriss)

    Fatal error: Call to undefined function add_filter()

    That’s not normal — add_filter() is a standard WordPress function (see https://developer.wordpress.org/reference/functions/add_filter/).

    Your debug.log contains no other errors?

    Aside from the (fairly well known) ImageMagick issue, this could also be caused by a badly coded filter which loops / recurses itself. Have you tried disabling all other plugins in turn? Knowing which plugin may have the badly coded filter would help…

    js.

    Thread Starter mpmorris

    (@mpmorris)

    Okay, thanks. I’ll go through the plugins one by one. I’ll also try a stock functions.php file.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Plugin causing WordPress to run out of memory’ is closed to new replies.