Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • 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
  • James Willenbring
  • Trilinos
  • Issues
  • #2327

Closed
Open
Created Mar 03, 2018 by James Willenbring@jmwilleMaintainer

PyTrilinos: memory leak with repeated creation of CrsMatrix and solver.Iterate

Created by: guyer

Repeated creation of CrsMatrixen and AztecOO solvers causes memory to steadily leak

Motivation and Context

We may be using PyTrilinos inappropriately, but FiPy creates a new CrsMatrix and AztecOO solver at each iteration. Because of this leak, we have no choice but to regularly checkpoint and kill the job.

Steps to Reproduce

Running this modified version of exAztecOO.py with

mprof run python exAztecOO.py

produces this plot leak

Your Environment

  • Relevant configure flags or configure script: Trilinos 12.10.1 installed from this conda feedstock
  • Operating system and version: Mac OS X 10.12.6 and Debian GNU/Linux 8 (jessie)

Additional Information

Based on earlier discussions on the FiPy mailing list the leak may have been introduced after version 11.10.2

Assignee
Assign to
Time tracking