This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
- | 8:00 – 13:00 | 9:00 – 13:00 | 9:00 – 13:00 | 8:00 – 12:00 | 8:00 – 12:00 | - |
- | 14:00 – 17:00 | 14:00 – 18:00 | 14:00 – 18:00 | 13:00 – 17:00 | 13:00 – 17:00 | - |
Supporter timezone: Europe/Zagreb (GMT+01:00)
Tagged: Exception
This topic contains 31 replies, has 2 voices.
Last updated by Bruno Kos 2 months, 2 weeks ago.
Assisted by: Bruno Kos.
Author | Posts |
---|---|
October 8, 2024 at 10:45 am #16264987 | |
kevinB-74 |
Website is still broken in production. |
October 8, 2024 at 12:23 pm #16265341 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
Can you please try the following: 1. Check your `php.ini` file and ensure that the value for `zend.max_allowed_stack_size` is set to `-1`. This is a new feature in PHP 8.3, and setting it to `-1` may help bypass the issue. More details can be found in the PHP 8.3 migration guide: [PHP 8.3 Other Changes](hidden link). 2. Verify if you or someone else manually set the values for `zend.reserved_stack_size` and `zend.max_allowed_stack_size` to `0`. The default setting in PHP 8.3.x for these values is `0`, but it's worth confirming if these were manually adjusted. Let us know if you have any questions on the matter. |
October 8, 2024 at 1:55 pm #16265784 | |
kevinB-74 |
Please confirm me that you want to put these values ? zend.max_allowed_stack_size = -1 |
October 8, 2024 at 2:15 pm #16265850 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
Yes, but note the following potential risks on WordPress: Server Overload: Removing the stack size limits might make the site more vulnerable to recursive function calls or resource-intensive operations, which could overload the server. Crashes or Unresponsiveness: If WordPress or any plugin uses deep recursion (for example, in a large query or loop), it may cause the site to crash or become unresponsive. Security Risks: Removing such limits can expose your site to denial of service (DoS) attacks if someone exploits a script that causes excessive recursion or memory usage. That being said, it might be worth testing these changes temporarily to see if it resolves your issue. Just remember to monitor the system closely and revert back if things start to behave unpredictably. |
October 8, 2024 at 3:30 pm #16266411 | |
kevinB-74 |
We put these values but website is still crashed |
October 9, 2024 at 7:20 am #16268221 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
Could you please provide the updated debug log after increasing the value? I also noticed you are using Cloudflare, so it might help to temporarily disable it, clear the cache, and, if possible, restart the server before running the tests again. |
October 9, 2024 at 12:17 pm #16270006 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
We managed to reproduce it, upon saving a post (product in our case) which is duplicated to the 2 other languages, we get that error. Can you set: zend.max_allowed_stack_size = -1 zend.reserved_stack_size = -1 After this clear the cache, and, if possible, restart the server before running the tests again. |
October 11, 2024 at 9:17 am #16278267 | |
kevinB-74 |
I didn't get the error again since october 8th... Do you think I can keep these values or it is too risky for security and then how can we do? Regards, |
October 11, 2024 at 11:28 am #16279250 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
These settings disable the stack size limits, which can present potential risks to security and stability in the long term. Until we can provide a permanent fix, you have a few options: 1. **Find Proper Limits:** 2. **Apply the Suggested Values:** 3. **Consider Downgrading PHP:** From what we understand, the issue may be caused by the excessive use of a particular function in your system. PHP could be mistakenly identifying this as infinite recursion, when in fact it is a **finite** recursion. We will continue to work on identifying a more stable and long-term solution. |
October 11, 2024 at 12:24 pm #16279615 | |
kevinB-74 |
Finally this values creates 500 internal server error : [11-Oct-2024 05:13:07 UTC] PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes) in /home/ipkkcji/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/utilities/class-debug-backtrace.php on line 133 I can't keep these values activated... |
October 11, 2024 at 12:25 pm #16279621 | |
kevinB-74 |
I downgraded to PHP 8.2 |
October 11, 2024 at 12:49 pm #16279730 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
I see - Allowed memory size of 1073741824 bytes exhausted is most likely caused by the same loop. I will keep this thread updated as soon as I get some information from our development team, as I have no other workarounds to share at the moment. |
October 17, 2024 at 11:52 am #16299948 | |
kevinB-74 |
I got another crash today : [17-Oct-2024 11:45:42 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /home/ipkkcji/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/fp/core/Fns.php on line 218 But I am on PHP 8.2 which is supposed to be OK |
October 18, 2024 at 6:33 am #16302797 | |
kevinB-74 |
My webserver doesn't want to start again. Always down : [18-Oct-2024 06:20:13 UTC] PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes) in /home/ipkkcji/public_html/wp-includes/functions.php on line 4909 |
October 21, 2024 at 6:23 am #16310328 | |
Bruno Kos Supporter
Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+01:00) |
PHP Fatal error: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 20480 bytes) in /home/ipkkcji/public_html/wp-includes/functions.php on line 4909 To get more information on what's causing this, you'll need to enable full error reporting so we can capture the full error stack. Here's what you'll need to do: 1. Edit the `wp-config.php` file in the root of your WordPress install. define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 1 ); @ini_set( 'log_errors', 1 ); This will log the full error details in a file called `wp-errors.log`, which should help us track down what's going on. Also, if you noticed any specific actions or steps that triggered this error (like installing a plugin or running a large process), or if you can reproduce it, please let me know. |
The topic ‘[Closed] fatal error’ is closed to new replies.