[wp-trac] [WordPress Trac] #52528: Possible unnecessary buffering of output data in wp-includes/functions.php

[WordPress Trac]

#52528: Possible unnecessary buffering of output data in wp-includes/functions.php
----------------------------+------------------------------
 Reporter:  Dekadinious     |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  5.6.1
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------
Description changed by sabernhardt:

Old description:

> Hello!
>
> I have to start by apologizing if I am in the wrong place, or if I am
> structuring this ticket badly. I don't have much experience here inside
> trac. I am unsure of the component this ticket should be attached to.
>
> I stumbled upon a fatal error when trying to load the WooCommerce status
> page. The system runs out of memory on line 4755 in wp-
> includes/functions.php.
>
> While the actual bug most certainly lies elsewhere, I got some hints from
> my host that the solution on line 4755 is not the best. I have no clue
> about this, but I thought I at least could submit a ticket and let the
> community decide!
>
> To paraphrase a translation, they say:
>
> wp-includes/functions.php line 4755 has an unnecessary buffering of
> output data that uses ob_start(). We can turn it off, but it's not very
> important. The underlying reason is the fact that there is a lot of
> output data that is getting returned to the browser. Probably an amount
> of data that is so big that there has to be a bug somewhere.
>
> This is not a ticket to handle the bug that returns way too much data,
> but it's a ticket to flag the possible issue of unnecessary buffering of
> output data in wp-includes/functions.php.

New description:

 Hello!

 I have to start by apologizing if I am in the wrong place, or if I am
 structuring this ticket badly. I don't have much experience here inside
 trac. I am unsure of the component this ticket should be attached to.

 I stumbled upon a fatal error when trying to load the WooCommerce status
 page. The system runs out of memory on
 [https://core.trac.wordpress.org/browser/tags/5.6.1/src/wp-
 includes/functions.php#L4755 line 4755 in wp-includes/functions.php].

 While the actual bug most certainly lies elsewhere, I got some hints from
 my host that the solution on line 4755 is not the best. I have no clue
 about this, but I thought I at least could submit a ticket and let the
 community decide!

 To paraphrase a translation, they say:

 wp-includes/functions.php line 4755 has an unnecessary buffering of output
 data that uses ob_start(). We can turn it off, but it's not very
 important. The underlying reason is the fact that there is a lot of output
 data that is getting returned to the browser. Probably an amount of data
 that is so big that there has to be a bug somewhere.

 This is not a ticket to handle the bug that returns way too much data, but
 it's a ticket to flag the possible issue of unnecessary buffering of
 output data in wp-includes/functions.php.

--

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/52528#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform