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

[WordPress Trac]

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

Comment (by adamsilverstein):

 > So this could maybe be addressed by doing a fields arg on all GET
 requests for the route, something like this for the preload:

 I had hoped this smaller change would be enough to solve the issue, but I
 still saw the autosave fire after load.

 I reviewed the [PR](https://github.com/WordPress/gutenberg/pull/7945)
 where this was added originally. It says:

 > Attempts to resolve an issue whereby the editor is unaware of the
 existence of
 a more recent autosave, resulting in attempts to perform an autosave fail.

 I was no longer able to reproduce this issue, so I think this is safe to
 remove.

 I pushed this change to a PR to run tests, then this should be ready for
 commit.

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