Hello Jan,
> I did a quick estimate by resizing my xterm to maximum (on 1600x1200
> with a rather tiny font, yielding 264 columns) and multiplying by 2
> for a possible xinerama/dualhead setup. The outcome was more than
> 512, so I increased it to 768.
I see. 512 is enough for my 1920x1200 btw. However. MAXSTR does have an
effect on every buffer allocated in screen which basically means that
screen blows up in size:
My main screen for example has 217Mbyte _RSS_ for 44 windows and a scrollback
buffer of 5000 lines per window.
(mephisto) [~] ps axxuww | head -1; ps axuwww | grep sithglan | grep SCREEN
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
sithglan 18194 0.0 21.0 221424 217812 ? Ss Jul22 3:58 bin/SCREEN -S
main -c .screenrc-main
Never the less increasing MAXSTR is a big step into the right direction.
> If it's that much of an issue, I'll change these parts of the code to
> allocate the buffers dynamically - but I don't think it's worth the
> effort.
There is more broken than that. For exmaple the following:
Use a caption like the following:
caption always '%H%{-b}%{= wb} %-Lw%{= wr}%50>%{+b}%n%f %t%{= wb}%{-b}%+Lw%{=
wr}%-017= %c %Y-%m-%d'
and open 40 windows (I have that in the configile, too)
Start screen in a xterm (80x25) now dettach and reattach on a xterm running
fullscreen on 1600x1200 => BOOM => Segfault (you have to open a few windows to
see that effect: like 40 or so)
But if you start screen in a Fullscreen xterm in the first place you never get
the SEGAULT. So screen seems to have a look at the wide of the terminal you
start it initial and uses that information to allocate internal buffers. I
never tracked it down (but it should be really easy to track it down) because
it always happens to me when I reattach my (at work started screen) at home (I
have bigger screen at home).
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
