Thanks for the information we’ve reached out to our colleagues in Mailchimp support for the support ticket information and thread. However, until we receive that information, I went ahead and did an investigation on the store in question.
Taking a look at this store, I was able to see that there are reoccurring Fatal Errors that stem from a PHP limit error:?
allowed memory size of 536870912 bytes exhausted (tried to allocate 1662322512 bytes) context: {"error":{"type":1,"file":"\/home\/vist3191\/cme-pro.com\/wp-content\/plugins\/debug-log-config-tool\/app\/controllers\/logcontroller.php","line":245},"backtrace":[{"file":"\/home\/vist3191\/cme-pro.com\/wp-content\/plugins\/woocommerce\/includes\/class-woocommerce.php","line":378,"function":"critical","class":"wc_logger","type":"->"},{"function":"log_errors","class":"woocommerce","type":"->"}]}
This in turn can be causing a bottleneck which results in a degradation in performance of the site and the WooCommerce Action Schedular in which Mailchimp uses to sync data.
Here’s what it means in the context of WordPress and WooCommerce:
The error occurred in the LogController.php file of the “Debug Log Config Tool” plugin on line 245.
The WooCommerce class (class-woocommerce.php) was trying to log an error on line 378, but this operation required more memory than was available to PHP.
PHP has a memory limit setting that restricts how much memory a script can use. In this case, the limit was set to 536870912 bytes (512MB), but the script tried to allocate 1662322512 bytes (around 1.5GB) of memory, exceeding the limit.
To resolve this issue, you can try the following steps:
- Increase the PHP memory limit by adding the following line to your WordPress site’s wp-config.php file: define(‘WP_MEMORY_LIMIT’, ‘1024M’); This will increase the memory limit to 1GB, which should be sufficient for most cases.
- Deactivate and remove the “Debug Log Config Tool” plugin, as it seems to be the source of the memory exhaustion issue in this case.
- Check for any other memory-intensive plugins (besides Woocommerce and Mailchimp) or operations on your site and try to optimize or disable them if possible.
- Finally once all above steps are completed, try kicking the sync into flowing by checking for pending?Scheduled Actions?under?WooCommerce?>?Status?>?Scheduled Actions?>?Pending. And click Run next to an Mailchimp WooCommerce Hooks.
It’s important to note that increasing the memory limit is a temporary solution, and it’s better to identify and fix the root cause of the excessive memory usage to prevent similar issues in the future. These memory issues aren’t being caused by Mailchimp in particular, but a combination of things that are outside the scope of our support we can provide without direct access to your server and hosting environment.
Once these mentioned server environment issues have been address it should help Mailchimp sync with a better performance.
