Plugin throwing HTTP 500 error

  • Resolved supahduck

    (@supahduck)


    8 years, 1 month ago

    Hello there, been using your plugin for the last two years without issue, until now.

    No special configuration on the plugin, just a small JPG at the top of the template. No custom fonts or anything like that.

    Turned on debug, and got the following error when attempting to generate a PDF packing slip:

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 122880 bytes) in /home/supahduc/public_html/northerncharms.ca/wp-content/plugins/woocommerce-pdf-invoices-packing-slips/lib/dompdf/include/page_frame_decorator.cls.php on line 394

    My install has 128MB available, and all other indicators are green, except for opcache and Gmagick.

    Any thoughts on the issue, as this has been working fine until now, and there hasn’t been any other changes to the WordPress / WooCommerce installation, other than the normal upgrades for installed plugins.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Ewout

    (@pomegranate)

    Hi! Nothing changed in the plugin that I can connect to a sudden increase in memory usage.
    The only thing I can think of is that there’s a specific product that is somehow causing extra long pages, which then chokes the plugin. Does this error also pop up with older orders?

    I have a rundown on solving memory issues in the documentation: https://docs.wpovernight.com/woocommerce-pdf-invoices-packing-slips/memory-issues/

    Let me know if that helps!
    Ewout

    Thread Starter supahduck

    (@supahduck)

    Ewout, thanks for the quick reply!

    Yes, the error comes up on older invoices / packing slips, that were successfully generated in the past, and on older orders where I hadn’t generated documents, as well.

    The products themselves are very basic, and don’t have a lot of data that gets embedded on the document…. the most I’ve ever had was two pages for a packing slip.

    I’m not using any custom fonts or CSS, it’s pretty much your vanilla install.

    I will look at the ‘memory issues’ doc and see if I can find anything….

    Chris

    Thread Starter supahduck

    (@supahduck)

    Ewout,

    It was a simple ‘lack of memory’ issue. My self-hosted install is fairly plugin-heavy (36 right now, about half of them fairly small but related to Woo, the rest are for WordPress), so I guess with all the recent upgrades for all these plugins, it’s been edging up to the 128M limit I had set.

    Upped it to 256M, and everything started working. Also put in

    define( ‘WP_MAX_MEMORY_LIMIT’, ‘256M’ );

    in wp-config.php, just in case.

    Thanks again for the advice and assistance! (You can mark this issue as resolved now. ?? )

    Plugin Contributor Ewout

    (@pomegranate)

    Great! Glad to hear that’s resolved ??

    Have a fantastic week!

    Ewout

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Plugin throwing HTTP 500 error’ is closed to new replies.