This may or may not be helpful but “CPU RAM memory (1GB)” is extremely low, I would recommend upgrading your hosting.
Thread Starter
khoavo
(@khoavo)
@rankbrands – I know but it’s been running fine up to WooCommerce v8.40. Not sure why WC v8.5.1 is causing this issue. I noticed some other users are experiencing the same issue (503 error, etc) when they installed WC v8.5.1. Been using Shared Hosting forever and no need to get dedicated hosting you know?
Thread Starter
khoavo
(@khoavo)
@hastibe – Thanks for the information, much appreciate it.
Hello @khoavo,
Thanks for reaching out.
It has come to our attention and our developers are aware of some of the issues caused by the latest WooCommerce release.
As @hastibe has shared, we are actively tracking any error issues that users are facing, and please feel free to submit an issue on GitHub as WooCommerce is an open-source project and all contributions are welcome.
Please let us know if you have any further questions or concerns.
We will be happy to help you further.
Thread Starter
khoavo
(@khoavo)
Thanks @ckadenge – WC 8.5.1 issue appears to affect only some web hosting servers, not all. For example, I have a site running WC 8.5.1 on the Godaddy web hosting server and there’s no issues there. But on others, WC 8.5.1 breaks the site and generates the 508 Resource Limit is Reached error, where it instantly uses up all the memory ram from the shared hosting server, etc.
I’ll wait for your team to release the next WC update so I can test it again. But for now, WC 8.40 is working fine on all of my sites.
Hi @khoavo,
We understand how frustrating it can be when things don’t work as expected.
However, this issue seems isolated, and our team is currently investigating it. It might be related to specific server configurations or certain plugins that might not be compatible with this version of WooCommerce.
In the meantime, we’re glad to hear that version WC 8.4.0 works well for you. We encourage you to continue using this version until we roll out the next update.
Meanwhile, I will mark this thread as resolved. Should you have further inquiries, kindly create a new topic here.
Thank you for your understanding and cooperation.
Hi @khoavo,
Thanks for taking the time to kick off this discussion and share all the information.
it breaks my site and also instantly max out my web hosting CPU RAM memory (1 GB) to the max of 100%, causing overload on the server
I noticed some other users are experiencing the same issue (503 error, etc) when they installed WC v8.5.1
Do I understand correctly you were getting 503 errors on your site? Were there any other error details available while the site was broken?
My WordPress Theme Developer and my Web Hosting Technical Team did a thorough debugging & troubleshooting, and they determined that it’s not related to the WordPress Theme, nor can they figure out why WC v8.5.1 crashes the site and sucks up all the CPU RAM Memory on the shared web hosting server.
During the investigation, have you found any error logs even if they might seem unrelated to the issue?
Thanks!
Thread Starter
khoavo
(@khoavo)
@karolmanijak – After the WC 8.5.1 update, I encountered this main issue: The Physical resources hit 100% (Shared Hosting Memory RAM). We even tried clearing all the running processes however the physical memory reached 100% as soon as the site was visited. We also tried to increase the PHP parameters that did not help.
As a result of this, I couldn’t even logged onto my wp-admin, it would show Internal Server Error, Exceeded Resources, Forbidden Access Not Allowed, etc. and on the live website, when viewed, all the images are not displayed, as if they’re broken. Probably due to the 100% resources maxed out from the WC 8.5.1 update.
But once I rolled back WC to v8.40, all works fine again. Hope this help answer your questions. I’ll just wait for the WC to release the next update once they figure out the fix for this.
Hi there @khoavo 👋
To clarify, did you already have a chance to test the maxing-out of hosting resources with only a default WooCommerce theme (like TT3), and WooCommerce activated, and see how it goes, or otherwise?
Thread Starter
khoavo
(@khoavo)
Hey @anastas10s – I sure did, installed and activated TT3 to test: https://prnt.sc/q3WoFPohr0gG
With WC v8.40 activated, TT3 Theme displays fine, my CPU and Physical Memory Usage on the server shows normal: https://prnt.sc/f3hgRE2j50-9
But as soon as I update to WC v8.5.1: https://prnt.sc/2h7lKOYKtESK – Within 10 seconds, the site breaks, wp-admin access and website pages won’t load, page not found, internal server error, etc. And the CPU and Physical Memory Usage gets maxed out at 100%, see: https://prnt.sc/YG8nZfmfbSBR
As I indicated before, the issue with WC v8.51 seems to affect some web hosting providers / servers only and not others. For example, I have another WordPress site running WC v8.51 on Godaddy.com shared web hosting server and there’s no issues there. The WordPress site that I have issues with while running WC v8.51 is on the Midphase.com shared web hosting server. Perhaps you can find out the type of server Midphase.com is using? Or ask other users that are currently experiencing the same issues with WC 8.51 and find out which web hosting providers they are using. Hope this helps you as you investigate for a fix.
But for now, WC 8.40 is keeping my WordPress site running fine.
-
This reply was modified 6 months, 2 weeks ago by
khoavo.
My experience is similar. Without extra plugins, only with Avada theme still active (otherwise more would break), so much resources are used, that I had to restart my whole server to get it under control again. I manage my own server and have only 1 site on that server with this issue. Multiple other sites are working fine with 8.5.1, so it’s not just the server, bad/limited hosting or anything, there’s an endless loop that eats up all the resources.
I noticed that lots of CSS files were loaded by the server IP (1000 times as much as other Woo 8.5.1 sites over a period of time). These were all in the directory /wp-content/plugins/woocommerce/assets/client/blocks/
In phpMyAdmin I also noticed lots of processes of this site with the status SLEEP, but even if I stopped them, they came back over and over faster than I could close them, so it’s also database related and of course both I/O and database calls can lead to a high server load.
Hi there @khoavo @josklever
From what I gather, it is either other plugins concurrently activated with WooCommerce version 8.5.1, or a theme other than a default ones (like TT3).
Just to clarify, in case the same resource-hogging behavior is noticed with one hosting provider (with the above-mentioned set up), and not with another, feel free to reach to their support channel(s) for further insights on this.
I trust that points you in the right direction. Do let us know how it goes, and if you have more questions.
We’re happy to help.
-
This reply was modified 6 months, 2 weeks ago by
anastas10s. Reason: added URL
As I explained I can’t do another test risking another meltdown of my server (impacting this site and 130+ other clients). I can tell that others sites on my server using Avada and WooCommerce don’t have any issues. And it’s not related to hosting as I’m sure my server could handle this in normal conditions.
And @khoavo already mentioned that the issue also happened with TT3.
It’s my job to maintain 300+ sites and investigate strange issues, so you have to trust me, that this is not a simple conflict with a theme, plugin or bad hosting.
Can you please investigate where all those CSS files are loaded? It must have something to do with the new integration of Woo Blocks.
Thread Starter
khoavo
(@khoavo)
@anastas10s – Bro, this issue is not caused by other plugins concurrently activated nor any by other themes. I told you my theme developer and web hosting provider did a thorough debugging process and concluded that WC 8.5.1 when activated hogs up all the CPU and Physical Memory on the server, crashing the site and server.
I even did my own test by activating TT3 default theme with all plugins deactivated accept for WC 8.5.1 and it broke my site and server. Something from WC 8.5.1 is hogging up all of the memory ram and CPU usage %.
