[wp-trac] [WordPress Trac] #62057: Addressing Autosave Memory Issues

[WordPress Trac]

#62057: Addressing Autosave Memory Issues
-------------------------------------------+-----------------------------
 Reporter:  whyisjake                      |       Owner:  (none)
     Type:  defect (bug)                   |      Status:  assigned
 Priority:  normal                         |   Milestone:  Future Release
Component:  Editor                         |     Version:
 Severity:  normal                         |  Resolution:
 Keywords:  has-patch dev-reviewed commit  |     Focuses:
-------------------------------------------+-----------------------------

Comment (by adamsilverstein):

 Thanks for the detailed analysis @tallulahhh - this is immensely helpful
 in understanding the scope of the issue.

 > Unfortunately per_page doesn't work for the autosaves route, so rather
 than changing the request in gutenberg, I had to change the response
 instead.

 Hmm, I wonder why? Maybe that needs fixing first. If it did work
 correctly, would that solve the issue (for many revisions OOM anyway)?

 We should make sure the fields key is supported so we can avoid requesting
 the autosave content if we don't need it.

 > To make testing easy, I made a mu-plugin that autosaves frequently with
 a different userID each time.

 Clever, thanks for sharing that.

 > As such, the autosave route only ever needs return one autosave.

 some use cases may want more than one though.

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