[Konsole-devel] [Bug 176974] High memory consumption when using Konsole for a longer time.

Matthew Woehlke mw_triad at users.sourceforge.net
Mon Jun 8 20:43:00 UTC 2009


--- Comment #35 from Matthew Woehlke <mw_triad users sourceforge net>  2009-06-08 22:42:57 ---
> #29, yes that's about what was proposed in #20

Was it? I understood that as separate arrays, whereas my suggestion was
everything packed into one unified buffer. (For that to be most useful,
however, you need to eliminate some abstraction and tie it pretty closely with
the painting code.)

> Don't forget that attributes are always present

Of course. As a design point, I assume that the buffer always starts with a
full attribute block. (While you *could* optimize that out - most lines are the
same, after all - you're now looking at quite some performance overhead
searching backwards to find out what are the current attributes for not enough

Personally, if I were doing the work, I think I would be doing something with
the 'everything is optional' attribute bitmask. But really, you need the
storage to tie directly into the painting code if you're going to get maximum
efficiency out of that. And there are still trade-offs to each possible

Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the konsole-devel mailing list