Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C cbl-gdb
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • COBOLworx
  • cbl-gdb
  • Issues
  • #62

Closed
Open
Created Jul 02, 2021 by rdubner@rdubnerOwner

CBREAK uses crt_malloc(), but doesn't call crt_free()

Allocated memory will, of course, be returned to the system when the inferior closes.

Each CBREAK allocates over 64K of memory, which is both large, and in modern computers, small. In a long session with a a lot of CBREAKing, it could become noticeable.

@sjaak, I think this one is probably yours, no?

Assignee
Assign to
Time tracking