The better question might be "if you want to turn it off, the question is why", or something.
The better question might be "if you want to turn it off, the question is why", or something.
ob_start();
include $file;
$contents = ob_get_contents();
ob_end_clean();I'd assume the 16x calls would be because they have a very complicated set of templates/layouts/partials, all doing their own templating.
I can see 16 calls over the lifetime of the request, but what was confusing me was how they could have 16 nested calls forming some ob_start();ob_start();...ob_end_flush(); Maybe some crazy way to avoid having to return text up the tree through function returns. But I read the post again and it said nothing about nesting them, so it's probably just something like 16 sub-templates or whatever as you suggest being processed at different intervals, not necessarily nested, with the gc not collecting frequently enough.
PHP is written in C which is not garbage collected.
PHP itself collects garbage, but this buffer is an internal C buffer and would be released immediately.