[wp-trac] [WordPress Trac] #24958: Large number of revisions cause memory exhaustion

[WordPress Trac]

#24958: Large number of revisions cause memory exhaustion
------------------------------------+------------------------------
 Reporter:  jshreve                 |       Owner:  adamsilverstein
     Type:  defect (bug)            |      Status:  assigned
 Priority:  low                     |   Milestone:  Future Release
Component:  Revisions               |     Version:  3.6
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+------------------------------

Comment (by adamsilverstein):

 Replying to [comment:22 callumbw95]:
 > Hey all,
 >
 > I just came across this ticket, and it got me thinking about
 [https://make.wordpress.org/core/tag/phase-3/ Phase 3] and how the new
 page collaboration may be affected by this issue. As collaboration will
 rely on post revisions, I can see the revision count growing quite a bit
 quicker in the future for a single post.

 I believe this issue relates mostly to the current Revisions UI which I
 expect will be replaced with the Phase 3 work. The ticket does mention
 failure on post update which could still be relevant, and we will need to
 make sure the new UI carefully considers working with a large number of
 (potentially large) revisions. One possibility to reduce sizes would be
 store only updates/changes for autosaves and only save the full post
 content for manual saves. Currently we save the full post content for
 every autosave or draft/post save.

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