Skip to content

Memory leak in connection pool handler #263

@stranske

Description

@stranske

Bug Report

Describe the bug
Memory usage grows continuously over time, eventually causing OOM errors.

To Reproduce

  1. Run the application for 24+ hours
  2. Monitor memory usage
  3. Observe steady growth even with no active connections

Expected behavior
Memory usage should stabilize after initial warmup.

Metrics

  • Initial memory: 512MB
  • After 24h: 4GB+
  • After 48h: OOM kill

Test Case: Fresh validation after PR #733 merge. Should get ONLY bug label.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions