[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:  3.6.1
Component:  Revisions     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+--------------------

Comment (by adamsilverstein):

 Replying to [comment:5 jshreve]:
 > Replying to [comment:2 adamsilverstein]:
 > > 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!
 >
 > The reason this was surfaced is because we have a test suite for the
 WordPress.com REST API that edits the same post over and over - therefor
 it quickly got to 1000+ revisions :). We could/should probably clear out
 the data after the tests run for certain things - but that's how it got so
 high.

 Tearing down your old test data would make sense, also you can limit the
 number of revisions WordPress stores, see
 [http://codex.wordpress.org/Plugin_API/Filter_Reference/wp_revisions_to_keep
 wp_revisions_to_keep]. In any case, we should still address the issues you
 raise in this ticket.

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