Exhausted memory error with Backtrace.php if this appears in code -apply_filters

UPDATE: In my block callback I was checking if (defined(‘REST_REQUEST’) && REST_REQUEST)) for backend detection to exit and presumably Query Monitor runs through my callback function before that’s true?
…so now I do this “if ((defined(‘REST_REQUEST’) && REST_REQUEST) || is_admin())” – and it exits as expected.

Maybe a flaw in my code and not Query Monitor? ??

I would have to dig into the code in QM to check exactly what it does with regard to detecting blocks within post content, but calling apply_filters('the_content', $post_content) on code that is itself processed within post content sounds risky because it can lead to an infinite loop. That might be what is happening in QM.

thanks John, you’re right with the recursion conclusion. No need to check your code, if query monitor didn’t burn out the memory something else would have ??

FYI the block I’m using is placed inside a Kadence element of type template. It is set to replace the post content template. So there’s no risk to frontend. However on the backend the problem arose because rest checks weren’t triggering my default preview id so I think it was attempting to load itself, as kadence element is a cpt. I think I’ve solved it with the addition of the is_admin() check.