gh-144067: Document terminal leak when initscr() follows setupterm()#152624
Open
serhiy-storchaka wants to merge 1 commit into
Open
gh-144067: Document terminal leak when initscr() follows setupterm()#152624serhiy-storchaka wants to merge 1 commit into
serhiy-storchaka wants to merge 1 commit into
Conversation
…erm() The curses library keeps a single current terminal: calling initscr() or newterm() after setupterm() abandons the terminal that setupterm() allocated without freeing it. This cannot be fixed safely in code (freeing the terminal would break the capsule API and pending terminfo queries), so document the behavior, with a cross-reference from initscr() and newterm(). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Documentation build overview
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document that calling :func:
initscror :func:newtermafter :func:setuptermleaks the terminal thatsetupterm()allocated: the curses library keeps only a single current terminal and does not free the previous one.This one-time libtinfo leak cannot be fixed safely in code -- freeing the terminal would break the capsule API and any pending terminfo queries (see the discussion on the issue) -- so the behavior is documented instead, with a cross-reference from :func:
initscrand :func:newterm.curses.initscraftercurses.setupterm#144067