Hi Radha,
>From the list:
the title
URI
nsILayoutHistoryState
nsIInputStream
numeric ID
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?
Radha Kulkarni wrote:
> Doug Turner wrote:
>
> > In the short term, I think that making this value a preference would be
> > great.
>
> Yes, the configuration will be thro' Pref. The option would probably go
> in to the History panel in the Pref UI
>
> >
> >
> > What is preserved with session history? Why cant we just save the top
> > level url or urls for a frameset instead of everything? Could you breifly
> > list what negative things would happen if I set the max entries of session
> > history to zero? Are there any?
>
> SH right now saves the title, URI, a handle to nsILayoutHistoryState,
> nsIInputStream(for postdata) for the page and a numeric ID used while
> going back/forward thro' the entries
>
> Title is used by the Go/Back/forward menus. nsILayoutHistoryState
> information is used to restore form values/srollbar positions. The
> nsIInputStream is used in reposting form submissions. There is a
> attribute to save the nsIDOMDocument, but is currently unused.
>
> If you set the Max entries to 0, no url will be saved in SH and
> therefore the back/forward buttons will be always disabled.
>
> >
> > Thanks,
> >
> >
> > Radha Kulkarni wrote:
> >
> >
> >> Session History currently grows unbounded and has occupied the #2 slot
> >> on the bloat chart. http://bugzilla.mozilla.org/show_bug.cgi?id=62651
> >> lists some of the ideas that have been thrown at the table. For 6.5,
> >> saving a limited (but configurable) number of entries in SH seems
> >> attractive.
> >>
> >> I'm not sure how affects the embedding world. Any ideas or issues with
> >> limiting the # of linear entries in SH?
> >>
> >> Thanks,
> >> Radha
