[wp-trac] [WordPress Trac] #57625: WP_Query cache memory leak

[WordPress Trac]

#57625: WP_Query cache memory leak
--------------------------+-----------------------------
 Reporter:  owi           |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Cache API     |     Version:  6.1
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  performance
--------------------------+-----------------------------
Changes (by spacedmonkey):

 * keywords:   => needs-patch
 * version:   => 6.1
 * milestone:  Awaiting Review => Future Release


Comment:

 Currently there is no patch or PR to fix this issue. A good starting place
 would be to get one ready so we can start the process.

 To be realistic, there fix will not go into the 6.2, this is too big of
 change to get in, so the earliest it will go into core, is 6.3. Which is
 months away. We have time here to work out a solution. If this is
 effecting your site on a day to day basis, then I would recommend turning
 the caching off, until a solution can be found in core. This is just
 returning you back to what core was like in 6.0-, so should not be too
 bad. You can also implement your solution using existing filters.

 To be clear, WordPress has to support lot of different types of object
 caching, including memcache, sqlite and redis. Not all of these support
 flushing cache groups. So any solution, will have to be a progrive
 enhancement. I will likely require object cache drop-in creators to do
 something. So again, this is not going to be a quick fix.

 > I am sorry that this sounds harsh but there is a clear flaw in how we
 handle wp_query keys in Core so we need a better solution and not
 questionable workarounds.

 I am not sure this kind of discourse is helpful to the discussion. It is
 not clear to me that there is a flaw in the core. I think it suboptimal is
 better way of putting it. But we trying to make solution for works for
 many type of object caching.

 I am willing to work on this ticket, let's try and work towards a solution
 and keep the conversion on a workable patch.

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