Fatal error with WC 9.6.0

  • Resolved ArcticFritid

    (@metuza)


    1 month, 3 weeks ago

    Hello.. After i updated WooCommerce to 9.6.0 i get a fatal error when saving taxonomies ie. product categories or product tags. There is no problems when saving WordPress categories or tags. It is a new site and i think way to small to have memory issues.

    • Error Level:?E_ERROR
    • Message:?Allowed memory size of 268435456 bytes exhausted (tried to allocate 593920 bytes)
    • File:?/wp-includes/class-wp-scripts.php
    • Line:?446
    • Request:?/wp-admin/term.php?taxonomy=product_tag&tag_ID=140&post_type=product&wp_http_referer=%2Fwp-admin%2Fedit-tags.php%3Ftaxonomy%3Dproduct_tag%26post_type%3Dproduct&message=3
    • Referrer:?/wp-admin%2Fterm.php%3Ftaxonomy%3Dproduct_tag%26tag_ID%3D140%26post_type%3Dproduct%26wp_http_referer%3D%252Fwp-admin%252Fedit-tags.php%253Ftaxonomy%253Dproduct_tag%2526post_type%253Dproduct
    • User ID: 1

    The issue appeared just after the woocommerce update. Any idea?

    I will another night test by deactivating plugins.

    Brgds
    Rune

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Reynier (a11n)

    (@reynierc)

    Hi @metuza

    Thanks for reaching out and providing details about what you’re experiencing. From the error message, it indicates that your site has reached its PHP memory limit, which is set to 256MB (that’s 268,435,456 bytes). The script tried to use an additional 580KB (593,920 bytes) but couldn’t because it exceeded this limit.

    Although your site is new and using the recommended memory limit, sometimes plugins or even themes can consume more resources than expected.

    You can try adjusting your memory limit by following this guide or contacting your host.

    If the issue persists even after this, we’d want to look into how your site is setup through a system status report. You can find it by going to WooCommerce → Status, selecting Get system report, and then Copy for Support.

    Thread Starter ArcticFritid

    (@metuza)

    Hello again,

    The wierd is that this site is a site i am setting up to replace my 5-6 year old site with 14900 orders and 3000 products, a site which has been used with 65 plugins, 256mb memory limit and no issues. It is just 2-3 months since i had to increase memory to 512.

    So that is the reason why i am concerned, this new site is very small, the same plugins (minus 10 plugins not used), and also HPOS active. Also database is just like a kid compared with the old site.

    Further testing today i did find that deactivating the YOAST Seo Locale plugin solved the issue like 90%. Not 100% ok but still fully usable.

    The main problem is that i am using Kinsta hosting and it has a cost at 50 dollars to increase memory to 512mb.

    Anyway, we will see what YOAST support can figure out in my staging site.

    Brgds
    Rune

    Plugin Support Reynier (a11n)

    (@reynierc)

    Hi @metuza

    Hmm, that’s indeed a bit of an odd situation given your experience with similar setups. It’s interesting that deactivating the Yoast SEO Locale plugin significantly improved the situation. Since it helped 90%, there might be some inefficiency in how it works with the new WooCommerce setup or with HPOS.

    It’s a good start to check with Yoast support. They may be able to optimize the plugin’s memory usage or find a specific conflict that can be resolved.

    It might also be a good idea to check your action scheduler under Tools > Scheduled Actions. In my experience, a large number of pending actions can potentially impact memory usage. But without the SSR, I wouldn’t know for certain. If you’re stuck, we can check for other angles once you send a system status report.

    Otherwise, feel free to keep us posted on any findings.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.