[wp-trac] [WordPress Trac] #60585: Recursion in WP_REST_Posts_Controller schema

[WordPress Trac]

#60585: Recursion in WP_REST_Posts_Controller schema
---------------------------------------------+-----------------------------
 Reporter:  derrickkoo                       |       Owner:  (none)
     Type:  defect (bug)                     |      Status:  new
 Priority:  normal                           |   Milestone:  Awaiting
                                             |  Review
Component:  REST API                         |     Version:
 Severity:  normal                           |  Resolution:
 Keywords:  needs-testing reporter-feedback  |     Focuses:  performance
---------------------------------------------+-----------------------------
Changes (by johnbillion):

 * keywords:  needs-testing => needs-testing reporter-feedback
 * version:  6.4.3 =>


Comment:

 Thanks for the ticket @derrickkoo and welcome to WordPress Trac.

 An object that contains deeply nested or fully recursive references
 doesn't ''necessarily'' consume a lot of memory because each of those
 objecss will be a reference to an instance rather than a copy (this is
 what allows a fully recursive property to exist on an object without
 exhausting all the available memory).

 I think we'll need some more info from you in order to investigate if
 there's an underlying problem and what its impact is.

 * Beyond identifying that recursive properties exist on the request object
 to a REST API endpoint, is there a concrete issue that can be seen? For
 example a memory leak.
 * You mentioned "this doesn't seem to cause an OOM error in my testing,
 but instead returns a 403 response". Are you able and willing to dig into
 this further to see if there is a cause for concern with regards to memory
 usage? Were you able to identify whether the 403 was related or caused by
 something else?

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