[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:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Revisions     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+------------------------------

Comment (by adamsilverstein):

 Wow, 1000+ revisions - that does seem like an edge case... none the less,
 crashing PHP is bad form and I agree we need some checks in place to make
 sure we don't do that.  I'm not sure about the first issue - the second
 one may be caused because the revisions page tries to pre-load all of the
 initial revision comparisons (so you can rapidly scroll thru them). The
 code is already capable of lazy-loading the data, and in fact thats what
 happens in the 'compare any two revisions' mode, we should be able to
 leverage that for large data sets like yours.

 We should probably only pre-load a set maximum number, then lazy load the
 rest. In our testing for 3.6 we tried posts with several hundred
 revisions, but never got to 1000!

--
Ticket URL: <http://core.trac.wordpress.org/ticket/24958#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software