Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 423
    • Issues 423
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1286
Closed
Open
Issue created Apr 15, 2019 by Mattijs Janssens@MattijsMaintainer

foamToEnsight leaks memory

Summary

valgrind reports some in-use memory after finishing. E.g. foamToVTK does not.

Steps to reproduce

valgrind --leak-check=full foamToEnsight

==3683== HEAP SUMMARY:
==3683==     in use at exit: 171 bytes in 4 blocks
==3683==   total heap usage: 67,611 allocs, 67,607 frees, 6,829,195 bytes allocated
==3683== 
==3683== 143 (72 direct, 71 indirect) bytes in 1 blocks are definitely lost in loss record 4 of 4
==3683==    at 0x4C2A6F0: operator new(unsigned long) (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==3683==    by 0x6921081: Foam::IOobjectList::IOobjectList(Foam::objectRegistry const&, Foam::fileName const&, Foam::fileName const&, Foam::IOobject::readOption, Foam::IOobject::writeOption, bool) (in /home/preston2/mattijs/OpenFOAM/work/develop/OpenFOAM-plus/platforms/linux64GccDPInt32Opt/lib/libOpenFOAM.so)
==3683==    by 0x44F58C: main (in /home/preston2/mattijs/OpenFOAM/work/develop/OpenFOAM-plus/platforms/linux64GccDPInt32Opt/bin/foamToEnsight)

Environment information

OpenFOAM version : develop

Assignee
Assign to
Time tracking