I have ACSS , Frames and Oxy-extras. I find its just a matter of the number of elements on a page.
I have gone in and added the following to my wp-config file:
define( ‘WP_MEMORY_LIMIT’, ‘256’ );
set_time_limit(180);
Memory limit was set to 180 which was what Bricks used to recommend. Looks like they changed to 256 sometime over the last couple of weeks.
We’ll see if this does anything to help.
With your post, I started researching and noticed that my WP_memory_limit was 40Mb 
I raised it to 256Mb, and I will report if there is any improvement.
Thanks for the info
For me this is not just Firefox anymore. Under 1.5.6, I also have a longer lag when I have multiple dynamic elements in a loop with conditions set in Brave. And this also extends to the front end and query times.
Ive had the same problem when trying to add custom css to a nestable slider that i was using to create a Menu card. Ive had quite a lot of divs in there.
I am fairly new to Bricks and I am facing the same issue with Firefox Developer Edition. Whenever I try to type on “search” field it takes 2-3 seconds to respond and the cursor moves out of the window too.
I am on a dedicated server (AMD 3600, 64GB RAM, 1TB NVME Disks), running PHP 8.2.13 -Dedicated FPM Application Served by Apache, (WP Memory Limit 1024MB)…well and the server is almost empty since it only has 2-3 low traffic brochure sites on it.
*I am not facing the same issue in Chrome, but I much prefer to use Firefox since it handles many windows/tabs open much better.
Hi @Jargon , welcome to the forum! If it’s only about the search, check this out:
This problem still exists with FF dev.
Is this being addressed?
Builder slows down to the point where it’s almost impossible to use.
Refreshing page doesn’t help.
the FF bug is marked as WIP, so means it’s being worked on.
I don’t think this is a Firefox only issue. Using Chrome my complex template may take more than 45 seconds to save. When I look at my server I see that I have the following message: * CPU resources limit was reached for your site.
When I contact A2 Support they initially said that heartbeat was sending a large amount of calls. So I disabled heartbeat. Issues continues. And it only happens when I’m in my template. For large complex pages I do not see the same issue.
I can work throughout my site all day and not have any lag. But the minute I go into the template its a complete slow down.
I think our problems are related, maybe you could tune in here: WAIT: Builder Lags and massive CPU Spikes when working with dynamic data - #6 by philipp
I checked an you are right, it is happening with my templates as well.
I’ve submitted my issue as well due to severe lag and 503 errors generated while working within a template. I noticed the issue back around version 1.8 but then it seemed to go away at least with 1.91 0r 1.92. Returned around 1.93 something.
I think the issue may be related to the setting in the image. The more custom fields included the more it seems to spike. But that’s just a guess. Going to try to turn the setting off (though I like my content populating in the builder) to see if it helps. Just not sure when I’ll be back working on this particular site. Maybe I’ll encounter it on another site.
