[vtkusers] VtkIdList and SetArray, allocation error

[Aron Helser]

Yes, I'd suspect the memory is getting freed twice - that's what "pointer
being freed was not allocated" probably means.
It's likely that both vtkIdList and numpy think they own the memory, and
can free it.

I'm not finding a reference on how to fix this issue, however. Could be
this blob series might suggest a better approach:
https://blog.kitware.com/improved-vtk-numpy-integration/

HTH,
Aron

On Fri, Apr 28, 2017 at 2:35 PM, foufara via vtkusers <vtkusers at vtk.org>
wrote:

> Thank you Andy for that quick answer.
> As I understand the message, yes this has to do with a bad usage of memory.
> But the message is odd. It says that my vtkIdList has been allocated at the
> time of freeing it, even though it seemed to work well giving me the rights
> Ids…How can it be ?
> And the error occurs at the time of quitting Python. So the memory has to
> be
> freed at that time…
>
>
>
> --
> View this message in context: http://vtk.1045678.n5.nabble.
> com/VtkIdList-and-SetArray-allocation-error-tp5743017p5743019.html
> Sent from the VTK - Users mailing list archive at Nabble.com.
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the VTK FAQ at:
> http://www.vtk.org/Wiki/VTK_FAQ
>
> Search the list archives at: http://markmail.org/search/?q=vtkusers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtkusers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20170428/9b7a881b/attachment.html>