I was using the Python curses module and I experienced this problem,
so I recreated a minimal example in C which still had the problem.
The problem seems to be triggered by this sort of procedure:
1. Write something to a window or pad.
2. Write something to another, scrollok, window or pad which causes it
to scroll.
3. Exit cleanly.
Result: The cursor is not restored to where it was before the program
started, rather it seems to stay where the last write left it.
Steps 1 and 2 can occur in the opposite order. The bug may or may not
occur given a certain combination of window size, location, and amount
of scrolling.
The problem occurs in PuTTY. It doesn't seem to occur in an XTerm.
Observed with library versions 5.6 and 5.7 so far.