Path: utzoo!attcan!uunet!wuarchive!psuvax1!gatech!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph R. Swick)
Newsgroups: comp.windows.x
Subject: Re: xterm mouse button bindings problem
Message-ID: <8910181220.AA03245@LYRE.MIT.EDU>
Date: 18 Oct 89 12:20:26 GMT
References: <4746@ncar.ucar.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: DEC/MIT Project Athena
Lines: 11

>   2) If I first hit button three, (with the mouse cursor in the window
>      for several seconds) invariably, the xterm is terminated.

Assuming you are using the default bindings, this action causes
xterm to attempt to extend the nearest end of the current selection
to the pointer position.  If this is the first thing you do, then
the other end of the selection is the first character in the
(scroll) buffer.  I'll bet you have a large saveLines resource
and that xterm is therefore trying to store a very large CUT_BUFFER0
property.  Xterm is buggy in that it doesn't intelligently handle
resource allocation failures of this nature...