Juergen Vigna <[EMAIL PROTECTED]> writes:

| On 12-Feb-2001 Jean-Marc Lasgouttes wrote:
| > 
| > Juergen> No IMO the problem is that a LyXText object is allocated at
| > Juergen> that time!
| > 
| > That's what I meant, in fact. Presumably, if the code needs to
| > allocate a new LyXText for the table, there also an old one in the
| > cache that should go away.
| > 
| 
| There is a cache but not in the tabular-inset, it's the InsetText which
| needs the LyXText and that is one per BufferView (which currently is fixed
| to 1 ;). So there is 1 LyXText for each BufferView for each InsetText AND
| the old one IS deleted if I reallocate it!
| 
| > Yes, the 1.2.0cvspatched is just that. One gains 2M (to compare with
| > memory consumption of around 50M!). This means that undo is really not
| > much, compared to lyxtext.
| 
| Ok this means we have to find a way to only use 1 LyXText instance, but
| how ... ???

Or lessen the mem consumption for a LyXText.

I have begun to remove a lot of memory consumption from LyXParagraph,
and a first for this is to introduce a ParagraphParameters class. I
have begun some of this in NEW_INSETS.

        Lgb

Reply via email to