← Back to team overview

dolfin team mailing list archive

Re: memory leak report in IntersectionDetector class

 

Hello,

Enabling Mpi and using mpic++ instead of c++ compiler in the installation.
solved this memory leak.

Best wishes,
Mehdi


Quoting Mehdi Nikbakht <M.Nikbakht@xxxxxxxxxx>:

> Hello,
>
> I am receiving memory leaks while running this simple code.
>
>   // Create mesh and function space
>   UnitSquare mesh(10, 10);
>   IntersectionDetector gts(mesh);
>
>   Point p;
>   p[0] = 0.3;
>   p[1] = 0.3;
>
>   std::vector<unsigned int> cells;
>   gts.intersection(p, cells);
>
> This is the output when I run valgrind with activating leak check flag,
>
> ...
> ==16411== 5,704 bytes in 23 blocks are possibly lost in loss record 2 of 3
> ==16411==    at 0x4023C4A: memalign (vg_replace_malloc.c:460)
> ==16411==    by 0x4023CFE: posix_memalign (vg_replace_malloc.c:569)
> ==16411==    by 0x5131352: (within /usr/lib/libglib-2.0.so.0.1800.2)
> ==16411==    by 0x5132B32: g_slice_alloc (in
> /usr/lib/libglib-2.0.so.0.1800.2)
> ==16411==    by 0x5132C34: g_slice_alloc0 (in
> /usr/lib/libglib-2.0.so.0.1800.2)
> ==16411==    by 0x511F791: g_node_new (in /usr/lib/libglib-2.0.so.0.1800.2)
> ==16411==    by 0x4340A52: gts_bb_tree_new (in /usr/lib/libgts-0.7.so.5.0.1)
> ==16411==    by 0x418A143: dolfin::GTSInterface::buildCellTree()
> (GTSInterface.cpp:201)
> ==16411==    by 0x418A4C1: dolfin::GTSInterface::GTSInterface(dolfin::Mesh
> const&) (GTSInterface.cpp:34)
> ==16411==    by 0x419BAD6:
> dolfin::IntersectionDetector::IntersectionDetector(dolfin::Mesh const&)
> (IntersectionDetector.cpp:30)
> ==16411==    by 0x8050077: main (main.cpp:50)
> ...
>
>
> Note that I am using the latest Dolfin built on Kubuntu 8.10 Intrepid.
>
> Best wishes,
> Mehdi
>
>
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev
>


References