Re: bin/50092: huge memory leaks in vi(1) when changing screen size

[Julian Coleman <jdc%coris.org.uk@localhost>]

The following reply was made to PR bin/50092; it has been noted by GNATS.

From: Julian Coleman <jdc%coris.org.uk@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: bin/50092: huge memory leaks in vi(1) when changing screen size
Date: Mon, 27 Jul 2015 12:21:17 +0100

 Hi,
 
 > I shall add one more comment. If you change the screen size rapidly,
 > sometimes you get error messages and additional memory consumption.
 > I guess that this is because a succeeding SIGWINCH interrupts the
 > reinitialization of screen due to a preceding SIGWINCH. It would be
 > better to neglect SIGWINCH during the (re)initialization of curses
 > screen. I'd like to hear your opinion.
 
 If we resize many times, we probably only care about the final size.  So,
 we really could ignore any apart from the last resize.  However, if we're
 already processing a resize, we should finish processing so that everthing
 is consistent (i.e. not interrupt the current resize).
 
 I wonder if we can just save the new size when we're already processing and
 check at the end of the current processing if a new (and different) size is
 saved?  Then we would re-run the resize with the new saved size.
 
 Regards,
 
 J
 
 -- 
    My other computer runs NetBSD too   -         http://www.netbsd.org/