Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.backend.python beat.backend.python
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.backend.pythonbeat.backend.python
  • Issues
  • #13
Closed
Open
Issue created Jan 12, 2016 by André Anjos@andre.anjos💬Owner

Memory leaks in the Python backend

Although most memory leaks have been mitigated with the release 0.1.3 of this package (optimization of struct.pack into numpy.tostring/numpy.tobytes), there seems still to exist a very mild memory leak. It is visible when one executes processes that access large amounts of data (such as in the Replay Attack dataset).

This problems needs to be investigated in a more closed setting for a leak-free execution.

Assignee
Assign to
Time tracking