Opened 4 years ago
Last modified 4 years ago
#52528 new enhancement
Possible unnecessary buffering of output data in wp-includes/functions.php
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | 5.6.1 |
| Component: | Administration | Keywords: | |
| Focuses: | Cc: |
Description (last modified by )
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.