rallel
> compositing issues, whether using a transparent boundary or point sprites).
>
> Best regards,
>
> Yvan
>
>
> - Mail original -
> De: "Andy Bauer"
> À: "Yvan Fournier"
> Cc: "Paraview (parav...@paraview.org)"
&g
Hi Yvan,
I have a merge request into VTK at
https://gitlab.kitware.com/vtk/vtk/merge_requests/3971 that hopefully
improves the memory use. I still have 2 tests that are failing and also
want to test with the ParaView tests so there's a bit more work to do. For
the most part it seems ok though so i
Hi Andy,
Thanks for checking. Fixing my own bug (by adding vtkSmartPointer where needed
in ly adaptor) fixed what seemed the larges issue on a small test case. A
colleague is testing this on a larger case (for a real application) and should
provide me some feedback on a larger, long-running case.
Hi Yvan,
The vtkPKdTree ones look like they could be after looking at the code,
especially vtkPKdTree::InitializeRegionAssignmentLists(). It seems like a
good idea to replace the int **ProcessAssignmentMap with maybe a
std::vector. Probably a good idea for the other member variables here as
well.