2009/8/11 Jean-Philippe Bernardy <[email protected]>: > > On Tue, Aug 11, 2009 at 6:44 PM, Colin McQuillan<[email protected]> > wrote: >> >> I found a leak that can't be fixed by seq. The *messages* buffer will >> still save undo information including everything that was ever shown. >> This patch will print increasingly big lines: > > There are two issues here. > > 1. As I mentioned previously that infinite undo is (in theory) problematic. > A solution would be to bound the depth of the undo lists somehow. > > 2. Lots of random stuff is put in the *messages* buffer. Some/most of these > are merely (very old) debug messages that can be safely removed. > > Even if these two issues are fixed, they can get in the way of debugging > leaks, > so it might be useful to have a flag somewhere that disable both undo and > messages.
When you had slow GC in Yi and were closing buffers did you kill *messages*? My automatic stress testing config does this now and I don't see any space leaks. It might be missing some behavior that triggers a leak though - any suggestions? Currently it opens a buffer, types a few characters, kills *messages*, kills the buffer, and repeats. --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list [email protected] http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
