DUPLICATE: Memory exhausted after updating to Bricks 2.2

Bugs
1

Hi Bricks team,

I know there is already a similar report about memory exhaustion related to dynamic data after the recent update, but in my case the problem is broader, so I want to report it separately.

After updating Bricks, the website started failing with PHP fatal memory errors.

What is different in my case is that this is not happening only when editing a page with Bricks.

The issue occurs:

  • on the entire frontend during normal page loads

  • in the WordPress admin area as well

  • not only inside the Bricks editor

So this seems to affect normal rendering of the site globally, not just a specific edit screen.

The repeated fatal errors in the log point mainly to:

  • wp-content/themes/bricks/includes/integrations/dynamic-data/dynamic-data-parser.php (line 30 and line 57)

  • and then secondarily also WordPress core files like:

    • wp-includes/class-wp-post.php

    • wp-includes/class-wp-object-cache.php

PHP memory limit is 256 MB, and the site keeps crashing with:

Allowed memory size of 268435456 bytes exhausted

Here is a sample from the log:

[05-Mar-2026 15:58:16 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home2/jlporhdx/public_html/wp-content/themes/bricks/includes/integrations/dynamic-data/dynamic-data-parser.php on line 30

[05-Mar-2026 15:59:51 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4096 bytes) in /home2/jlporhdx/public_html/wp-includes/class-wp-post.php on line 255

[05-Mar-2026 15:59:52 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home2/jlporhdx/public_html/wp-content/themes/bricks/includes/integrations/dynamic-data/dynamic-data-parser.php on line 30

[05-Mar-2026 16:13:47 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4096 bytes) in /home2/jlporhdx/public_html/wp-content/themes/bricks/includes/integrations/dynamic-data/dynamic-data-parser.php on line 57

[05-Mar-2026 17:32:31 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4096 bytes) in /home2/jlporhdx/public_html/wp-includes/class-wp-object-cache.php on line 379

From the log, the main trigger appears to be the Bricks dynamic data parser, while the WordPress core errors look more like secondary failures after memory is already exhausted.

I understand there is already a related topic, but I want to stress that in this case:

  • it affects the full website frontend

  • I also see errors in wp-admin

  • it is not limited to opening/editing a specific page in Bricks

Please let me know if you want the full log, environment details, or help testing a fix.

Thank you.

2

Question here, do you have any large queries or areas that is pulling large amounts of dynamic data? A recently added or modified template in Bricks that uses complex dynamic data queries.

Do you have any additional plugins that adds a lot of data for Bricks to process on a single page (like a custom post type with many fields) or Bricks related plugins?

A specific page on your site that is trying to load an enormous amount of information at once?

Also, have you tried to increase your memory to 512MB to see what happens?

3

Hi Jiří,
Thanks so much for your report!

If you send us your login details, we could test whether it is due to the dynamic data problem, and if not, check what the issue is on your end.

Also, please review Bricks » System information to rule out any bottlenecks (anything that isn’t green should be improved).

Best regards,
timmse

4

Ok, I see the site has very low RAM limit. 40 MB. I will try to increase it. In the meanwhile I sent you the credentials for staging site. Thank you!

UPDATE: Increasing the limit to 512 MB did not help.

image
image709×698 34.4 KB

5

Hi @jiripaulas

As per my email reply, it’s a bug in Bricks.

I installed the patched version of 2.2 on your site, it should be working now.

Please follow this thread discussion WIP: Error 500/Critical Error Memory Exhausted if image element with incorrect value on Dynamic data field

Regards,
Jenn