News for hackers. Stuff that matters.
Re:PHP's ob_start() pre-allocates 40k memory per call by Jach on Thursday December 08, 2011 @12:24PM (#3330013)
That's actually exactly what I was doing in the full context.

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.

Re:PHP's ob_start() pre-allocates 40k memory per call by ars on Thursday December 08, 2011 @04:52PM (#3331330)
> 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.

Re:PHP's ob_start() pre-allocates 40k memory per call by Jach on Thursday December 08, 2011 @08:00PM (#3331984)
...Yeah, not sure what I was thinking with that one, thanks for replying. (My excuse! I've been up over 24 hours already...)