You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer the following questions for yourself before submitting an issue.
I am running the latest plugin version
I am running the latest WordPress version
I know what PHP version I'm using
I checked the documentation and found no answer
I checked to make sure that this issue has not already been filed
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
WordPress version: 6.3.1
PHP Version: 7.4
JWT Authentication for WP-API Version: 1.3.4
Expected Behavior
Not crash the cron queue
Current Behavior
The new statistic cronjob added in 0cfb8e5 seems to be crashing the cron schedule resulting in the queue filling up rapidly. This resulted in the website of our customer crashing their entire server with 24 Cores and 64 GB of memory into OOM errors and taking their store and product down for about 2 days now. We just disabled the plugin for now as we don't necessarily need it but this should be either addressed or communicated immediately to prevent other users from running into similar issues potentially loosing a lot of users and money because of system crashes.
The text was updated successfully, but these errors were encountered:
Issue Name
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
Expected Behavior
Not crash the cron queue
Current Behavior
The new statistic cronjob added in 0cfb8e5 seems to be crashing the cron schedule resulting in the queue filling up rapidly. This resulted in the website of our customer crashing their entire server with 24 Cores and 64 GB of memory into OOM errors and taking their store and product down for about 2 days now. We just disabled the plugin for now as we don't necessarily need it but this should be either addressed or communicated immediately to prevent other users from running into similar issues potentially loosing a lot of users and money because of system crashes.
The text was updated successfully, but these errors were encountered: