Critical Error for Live Builder on Pages

[Gabriel]

#883129

Randomly, Avada Live Builder is showing a “Critical Error” on pages (not Blog posts) and it seems to be causing a spike/excess in memory usage. Our host give us more than enough to run Avada (256 MB) and it was working just fine a few days ago. Nothing major changed on the site.

We already turned off all the plugins except Core and Builder and it did not resolve the issue. We also tried uninstalling and reinstalling Core and Builder from the Avada dashboard and cleared Avada and website cache with no success.

Has anyone else experience this issue?

We are running Avada 7.7.1
Avada Core 5.7.1
Avada Builder 3.7.1
Wordpress 6.0

[Gabriel]

#883130

Update this is the error: PHP Fatal error Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in [oursiteurl]_480/public/wp-includes/meta.php on line 1189

[Gabriel]

#883169

I believe this is a bug introduced by the patch #420596 release on Jun. 8, 2022

[Ammar. S]

#883221

Hello Everyone

Memory size needs to be increased if its getting exhausted by any reasons following the instructions here please => https://theme-fusion.com/documentation/avada/technical/fatal-error-allowed-memory-size-exhausted/

There is no bug introduced with the patch 420596, also the patch is not required anymore as we have already released our latest version 7.8 so you should be able to update to that.

Thanks

-Ammar

[Gabriel]

#883244

Hi Ammar,

Our memory limit is at 256MB way more than limit suggested in this documentation. This didn’t start happening until that patch was installed and it only affects pages and not blogs. Updating to 7.8 did not fix the issue. Are the requirements to run Avada more than 256MB?

Thanks

[Ammar. S]

#883329

Hello @Gabriel

256MB is actually good enough memory, however this could be that you have a number of 3rd party plugin(s) here, I can only provide a solid response after taking a look into the site, I am sending you an email on the registered email address so please get back to me there further.

Thanks

-Ammar

[Gabriel]

#883378

It can’t be a 3rd party plugin issue because we disabled all of them on our staging environment (where the issue was replicated) and the issue was still happening. I have responded to your email.

Thanks,
Gabe

[Ammar. S]

#883444

Hello Gabe

I have got it, we suggest you to please communicate with us there 🙂

Thanks

-Ammar

[Author]

Posts