In article <[EMAIL PROTECTED]>, Doug Turner
<[EMAIL PROTECTED]> wrote:
> Radha Kulkarni wrote:
>
> > Doug Turner wrote:
> >
> > > it sounds like (based on no real data) that the
> > > nsILayoutHistoryState reference holds onto alot of stuff in terms
> > > of memory footprint. Do you have any feeling as to exactly what
> > > it costs to mantain form values and scrollbar positions?
> > >
> > Bug http://bugzilla.mozilla.org/show_bug.cgi?id=62651 is about
> > reducing the size of nsIlayoutHistoryState owned by Pollmann. There
> > are some #s on how much this structure is using and how it can be
> > reduced.
>
> Thanks for the bug number. We should make saving the
> nsILayoutHistoryState in session history optional. In the short
> term, this should be a big win for devices/applications that do not
> care about saving form data or scrollbar position.
I vote for the layered approach, where we only save form and scroll
state for the last N URLs (N perhaps dependent on memory pressure),
so go back and purge old history entries of non-essential data.
Simon
--
Simon Fraser Entomologist
[EMAIL PROTECTED] http://people.netscape.com/sfraser/
