Bug: PHP error when trying to edit image elements in Enfold Avia

Following on from this – This could be caused by an assumption being made in the code somewhere.

We have changed the PHP version back to version 8.2 latest.

But this time added wp-config define memory limit and max memory limit lines stating 2gb max memory limit.

The actual limit in the php settings is 4gb. but 2gb is the post max size so dont want the usage to exceed this ideally. These figures are the same for all of the php versions on our server. The only change is we defined it in WP-Config for the site.

Upon first attempt this has worked. But quite often this has been the case so need to keep an eye on the issue.

I guess we need to determine if anything in Enfold specifically related to the ALB image element looks for the memory limit?

Can you let me know how we proceed with this?

• This reply was modified 5 days, 16 hours ago by thinkjarvis.

Hi Rikard,

We used query monitor – It doesnt tell us anything useful.
It appears there is a memory leak somewhere or something in Enfold is picking up the wrong memory limit when it isnt specified.

For our site we just had to tell wordpress what the memory limits are by adding the following to wp-config.php
For us the 2gb limit per action looks like this:

define('WP_MEMORY_LIMIT', '2048M');
define('WP_MAX_MEMORY_LIMIT', '2048M');

For some reason the error code in the console was suggesting that the memory limit was around 512mb (written in bytes).

For context we actually have a 4gb memory limit – So there shouldnt have been a problem anyway but specifying a figure in wp-config seems to have solved the issue. I’ll report back if I can recreate it again.

The problem does not occur in PHP 8.0 but does occur in all versions above this.
With this in place the problem seems to have stopped and we are running PHP 8.2 again now. So it looks like there is an issue with the memory allocated to some actions in Enfolds interface not able to use the available ram fully.

Someone else reported a simillar issue here:

I was writing a reply on the post above explaining this when you closed it too early!!!!
Can you reopen it and add my suggestion above!

Hi both site health and woocommerce system info show the 4gb max limit. I set 2gb because 4gb is too large and overkill.

We run our own dedicated servers so it’s no issue with the provider. We set our own settings.

I can confirm that there is nothing wrong with the PHP, MySQL, mariadb or Plesk config.

The issue is for some reason some actions in the enfold builder are unable to allocate the required memory.

My suggested solution forces WordPress to recognise the correct memory limit.

As above the problem does not occur in php8 but started in php8.1 and above. I also checked the individual php fpm memory settings for each version.

Adding the memory limit to the wp-config forces WordPress to accept the new value and appears to stop the process hitting a false memory limit.

If this has fixed the problem then you guys need to investigate a possible memory leak or bug in the Avia builder in php8.1 and above.