Saving an ACF field group creates infinite loop, causing memory to run out.

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client was experiencing a fatal error due to running out of memory when trying to change the translation setting for a certain field in a field group, despite increasing the PHP memory limit up to 8GB.
Solution:
We recommended checking the WP Memory settings in addition to the PHP memory settings, as both are crucial for the operation. We advised increasing the WP Memory Limit to at least 256MB by adding the following lines to the wp-config.php file:

define('WP_MEMORY_LIMIT', '256M');<br />define('WP_MAX_MEMORY_ LIMIT', '256M');

We also performed standard WPML troubleshooting actions which seemed to resolve the issue temporarily. If the problem reoccurs, we suggested that the client should provide access to their site for further investigation.

Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.

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.

Tagged: Exception

This topic contains 7 replies, has 3 voices.

Last updated by Bobby 1 year ago.

Assisted by: Bobby.

Author	Posts
May 13, 2024 at 1:58 pm #15621268
Maurice Kruse	I am trying to: Change the translation setting for a certain field in a field group Link to a page where the issue can be seen: Backend. Details can be provided if necessary. I expected to see: The field group saving the setting Instead, I got: A fatal error due to running out of memory. Note that I already tried to increase the amount of available memory for the application in PHP settings. On my local version of this website I even boosted it up to 8GB but I get the same result after some time.
May 13, 2024 at 8:28 pm #15622460
Lauren WPML Supporter since 10/2015 Languages: English (English ) Timezone: America/New_York (GMT-04:00)	Thank you for contacting WPML support. While you are waiting for one of my colleagues to take this ticket and work on it, let me provide you with first debugging steps or if I can perhaps help with the issue quickly. There are two different types of memory, one is PHP and one is WP Memory. If you go to WPML -> Support and scroll to the bottom, what is the setting you have for WP Memory? It sounds like that will need to be updated in order for you to save the fields. Please try increasing the WP Memory Limit. Minimum requirements are 128Mb: https://wpml.org/home/minimum-requirements/ You can add this to wp-config.php to increase WP memory: /** Memory Limit / define('WP_MEMORY_LIMIT', '256M'); define( 'WP_MAX_MEMORY_LIMIT', '256M' ); Add it above the line / That's all, stop editing! Happy blogging. */
May 14, 2024 at 8:49 am #15624144
Maurice Kruse	Hello Lauren, Both the memory limit as well as the max memory limit are already set at 512M. This is also reflected by what can be seen at the support page from WPML. On my local runnning version of this website I even cranked it up to 8 GB for both values, but this doesn't solve the problem. The sving proces only takes a lot longer before the creash happens, since it takes longer for an infinite loop to fill up 8 GB of data.
May 14, 2024 at 7:35 pm #15626846
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Hi, Please share with me the exact field or page that is experiencing this behavior, or is it happening with all pages? I would like to request temporary access (wp-admin and FTP) to your site to test the issue. (preferably to a test site where the problem has been replicated if possible) Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/ You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you enter is private which means only you and I have access to it. NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin. Thank you, Bobby
May 17, 2024 at 7:36 pm #15640880
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Thank you, still reviewing this and will update you shortly
May 17, 2024 at 10:02 pm #15641182
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Hi there, I have tried to reproduce the issue but cannot at the moment. Do note that I ran some standard WPML troubleshooting actions which might have resolved the issue. These are the steps I take: ACF -> Field Groups-> Sections -> Copy once to Copy --> works OK Sectie -> Halve achtergrond inschakelen sectie -> Copy once to Copy -> works OK Is there a specific field that Is causing this behavior?
May 23, 2024 at 8:00 am #15660962
Maurice Kruse	Hi Bobby, I just found the time to check in on the issue, and it seems that whatever you did solved the issue. Before you changed anything every time I tried to change a random field's translation setting the infinite loop occurred. This seems solved for now. If I encounter it again I will contact you again with specific instructions on how to reproduce the issue. Thanks for the assistence!
May 28, 2024 at 1:36 pm #15678921
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	I am glad to hear that the issue has been resolved now!