ees this and can chime in.
>
>
> Thanks!
>
>
> Tim
>
>
>
>
> From: Burlen Loring <burlen.lor...@gmail.com>
> Sent: Monday, May 23, 2016 3:30 PM
>
> To: Gallagher, Timothy P; Andy Bauer
> Cc: paraview@parav
Bauer
Cc: paraview@paraview.org
Subject: Re: [Paraview] Memory leak with Catalyst
I think there is an api in the multi-block writer to disable writing metadata.
Utkarsh knows, he's the one that figured it out. not sure how it applies to
your use case. you may not even be using multi-block
*Sent:* Sunday, May 22, 2016 10:30 PM
*To:* Gallagher, Timothy P; Andy Bauer
*Cc:* paraview@paraview.org
*Subject:* Re: [Paraview] Memory leak with Catalyst
btw, we just had similar problem that was entirely explained by vtk
writer attempting to gather a bunch of arrays to the root node.
Utkarsh
, 2016 10:30 PM
To: Gallagher, Timothy P; Andy Bauer
Cc: paraview@paraview.org
Subject: Re: [Paraview] Memory leak with Catalyst
btw, we just had similar problem that was entirely explained by vtk writer
attempting to gather a bunch of arrays to the root node. Utkarsh found a way to
disable that be
work!
Tim
*From:* Burlen Loring <burlen.lor...@gmail.com>
*Sent:* Friday, May 20, 2016 3:46 PM
*To:* Gallagher, Timothy P; Andy Bauer
*Cc:* paraview@paraview.org
*Subject:* Re: [Paraview] Memory leak with Catalyst
VTK_DEB
,
Tim
From: ParaView <paraview-boun...@paraview.org> on behalf of Gallagher, Timothy
P <tim.gallag...@gatech.edu>
Sent: Friday, May 20, 2016 4:17 PM
To: Burlen Loring; Andy Bauer
Cc: paraview@paraview.org
Subject: Re: [Paraview] Memory leak with Catal
From: Burlen Loring <burlen.lor...@gmail.com>
Sent: Friday, May 20, 2016 3:46 PM
To: Gallagher, Timothy P; Andy Bauer
Cc: paraview@paraview.org
Subject: Re: [Paraview] Memory leak with Catalyst
VTK_DEBUG_LEAKS, although will catch some serious errors, will not catch all
kinds of
lagher, Timothy P
*Cc:* paraview@paraview.org
*Subject:* Re: [Paraview] Memory leak with Catalyst
Hi Tim,
If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good
at finding VTK objects that aren't deleted properly. You should be
able to run this with a small amount of calls to Catalyst a
Friday, May 20, 2016 2:39 PM
To: Gallagher, Timothy P
Cc: paraview@paraview.org
Subject: Re: [Paraview] Memory leak with Catalyst
Hi Tim,
If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good at finding
VTK objects that aren't deleted properly. You should be able to run this with a
Hi Tim,
If you build Catalyst with VTK_DEBUG_LEAKS enabled it is pretty good at
finding VTK objects that aren't deleted properly. You should be able to run
this with a small amount of calls to Catalyst as well. If you try this and
want help understanding the output (if an object like a
Hi,
One of our users is running a very big simulation and writing out images of two
slices (two different views) every 1000 iterations and writing out the data for
the two slices (two different data writers) as VTK files every 5000 iterations.
It is using Paraview 4.4.
After 21000
11 matches
Mail list logo