[wp-trac] [WordPress Trac] #52527: Better RAM handling in wp-db.php
WordPress Trac
noreply at wordpress.org
Mon Feb 15 11:26:08 UTC 2021
#52527: Better RAM handling in wp-db.php
-------------------------+-----------------------------
Reporter: Dekadinious | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Database | Version: 5.6.1
Severity: normal | Keywords:
Focuses: |
-------------------------+-----------------------------
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 stumbled upon a fatal error when trying to load the WooCommerce status
page. The system runs out of memory on line 2022 in wp-db.php.
While the actual bug most certainly lies elsewhere, I got some hints from
my host that the solution on line 2022 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/wp-db.php line 2022 is a bad solution because of a database
call that loads all results into RAM instead of iterating them one by one.
But independent of this the error seems to be caused by a very large SQL-
query that returns way too much data. Probably 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 bad RAM handling in wp-db.php.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/52527>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list