🚀 go-pugleaf

Macwrite has been misbehaving on me.  When I got my mac+ (running 3.1.1)
it would bomb several times a week.  The bombs took the form in infinite
loops that appeared when I was sweeping out an area of text and then typing
the replacement text.  Macwrite would occasionally hang there because the
handle in low memory that points to the clipboard had changed to zero and
macwrite was coded to loop until it was non-zero.

After upgrading to 3.2, I breathed a sigh of relief when after several weeks,
these bombs seemed to go away.  However, this morning while entering text,
macwrite provided a rather spectacular bomb by apparently eating through
memory (the screen turned into narrow vertical bars).

Does anybody know why macwrite is so anti-social on the Mac+ and is there
anything that can be done to prevent these bombs?

Thanks in advance.
   Marsh Gosnell   ihnp4!lzma!mkg