- Any implementation of curses must not free the memory as-
- sociated with a screen, since (even after calling <STRONG>endwin</STRONG>),
- it must be available for use in the next call to <STRONG>re-</STRONG>
- <STRONG><A HREF="refresh.3x.html">fresh(3x)</A></STRONG>. There are also chunks of memory held for per-
- formance reasons. That makes it hard to analyze curses
- applications for memory leaks. To work around this, one
- can build a debugging version of the ncurses library which
- frees those chunks which it can, and provides these func-
- tions to free all of the memory allocated by the ncurses
- library.
+ Any implementation of curses must not free the memory associated with a
+ screen, since (even after calling <STRONG>endwin</STRONG>), it must be available for use
+ in the next call to <STRONG><A HREF="curs_refresh.3x.html">refresh(3x)</A></STRONG>. There are also chunks of memory held
+ for performance reasons. That makes it hard to analyze curses applica-
+ tions for memory leaks. To work around this, one can build a debugging
+ version of the ncurses library which frees those chunks which it can,
+ and provides these functions to free all of the memory allocated by the
+ ncurses library.