Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A amdis
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • iwriwr
  • amdis
  • Issues
  • #4
Closed
Open
Issue created Nov 23, 2016 by Reuther, Sebastian@sreutherMaintainer

Memory leak in PETSc solver

If the initfile solver options "remove rhs null space" or "has constant null space" are enabled the memory starts to blow up. Probably the problem is in the PetscSolverGlobalMatrix::solvePetscMatrix() method. A SystemVector is created in the heap and it is never deleted - at least I cannot see it.

Assignee
Assign to
Time tracking