<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
After a lot of debugging, it turns out the issue is with the
SetCells function of the vtk unstructured grid. Below are the bits
of my Programmable Filter code that are relevant to the seg fault:<br>
<br>
<blockquote>output = self.GetOutputDataObject(0)<br>
<br>
cellArray = vtk.vtkCellArray()<br>
cellTypes = []<br>
<br>
# Create a polygon to display the selected points<br>
polygon = vtk.vtkPolygon()<br>
polygon.GetPoints().DeepCopy(pointArray)<br>
polygon.GetPointIds().SetNumberOfIds(len(coordinates)) <br>
for i in range(len(coordinates)):<br>
polygon.GetPointIds().SetId(i, coordinates[i][0])<br>
<br>
# Add the polygon to a list of Cells<br>
cellArray.InsertNextCell(polygon)<br>
cellTypes.append(vtk.VTK_POLYGON)<br>
<br>
# Get the cell containing a given cell & add it to the
cellArray<br>
selectedCell = input.GetCell(cellID) <br>
cellArray.InsertNextCell(selectedCell)<br>
cellTypes.append(vtk.VTK_TETRA)<br>
<br>
# SetCells of the output with only the selected analyzed cells<br>
output.SetCells(cellTypes, cellArray)<br>
</blockquote>
The last line above seg faults on one of my computers but not on the
other one, both using Linux Mint 15 OS, and similar versions of
ParaView. Any thoughts?<br>
<br>
<br>
<div class="moz-cite-prefix">On 15-01-28 07:27 PM, Omid Mahabadi
wrote:<br>
</div>
<blockquote cite="mid:54C97E84.80003@geomechanica.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hi,<br>
I've been experiencing a very weird seg faults in various versions
of ParaView (4.1.x, 4.2.0, 4.3.x) when running an animation
(streaming over time) of my Programmable Filter. I'm not even sure
this is a ParaView issue, but I'll still share my story in case
someone has any insights that they can kindly share.<br>
<br>
My Programmable Filter code works fine for the Current time step,
regardless at which time step I run it (i.e., hit the Apply button
of the Programmable Filter). However, when I hit the Play button
to loop over time steps (which appends some information to a CSV
file), ParaView seg faults after reaching the <i>3rd time step</i>.
The filter has been working for some time and this started to
happen all of a sudden, without any system update. <br>
<br>
It may be related to a weird combination of hardware, software,
and drivers. My script works fine on a desktop computer I have but
it seg faults on my main workstation, which has an AMD/ATI Radeon
R9 280x GPU running on Linux Mint 15, 64-bit. When I completely
removed the AMD drivers, it still seg faulted but after reaching
the <i>6th time step</i> after the current one. Then, I launched
an Ubuntu 14.04 LTS 64-bit, live on a USB flash drive. The script
in Programmable Filter worked perfectly fine. As a result, I
installed the OS, but it acted up exactly as the Linux Mint
installation. <br>
<br>
The input files are massive vtk unstructured grids (about 800 MB
each). I created smaller files, but unfortunately I couldn't
reproduce the error. But I'm fairly sure that the files are not
corrupted. As such, I can't send out the files that cause the
issue. I also monitored the memory usage using free -h command
while Playing. Here's the output for the "-/+ buffers/cache" line:<br>
<br>
<blockquote><small> total used
free<br>
-/+ buffers/cache: 7.2G 8.4G (Opening the .vtu
files)<br>
-/+ buffers/cache: 7.2G 8.4G<br>
-/+ buffers/cache: 7.4G 8.2G<br>
-/+ buffers/cache: 7.6G 8.0G<br>
-/+ buffers/cache: 7.6G 8.0G<br>
-/+ buffers/cache: 7.6G 8.0G<br>
-/+ buffers/cache: 7.9G 7.7G<br>
-/+ buffers/cache: 8.3G 7.4G<br>
-/+ buffers/cache: 8.5G 7.1G<br>
-/+ buffers/cache: 8.6G 7.0G<br>
-/+ buffers/cache: 8.5G 7.1G<br>
-/+ buffers/cache: 8.5G 7.1G<br>
-/+ buffers/cache: 8.5G 7.1G<br>
-/+ buffers/cache: 8.5G 7.1G<br>
-/+ buffers/cache: 8.6G 7.0G<br>
-/+ buffers/cache: 8.9G 6.7G<br>
-/+ buffers/cache: 9.1G 6.5G<br>
-/+ buffers/cache: 9.3G 6.3G<br>
-/+ buffers/cache: 9.4G 6.2G (Seg faults here)<br>
-/+ buffers/cache: 7.0G 8.6G<br>
</small></blockquote>
As you can see, my system still had a lot of free memory when the
seg fault happened and I haven't done anything explicitly to limit
memory usage by a single process. <br>
<br>
Looking at syslog, this is the error message for the seg fault:<br>
<blockquote>kernel: [77995.911073] paraview[22483]: segfault at
7f3c8e0398ac ip 00007f3a47ebe169 sp 00007fff9106ab50 error 4 in
fglrx_dri.so[7f3a479e9000+21e9000]<br>
</blockquote>
<br>
Am I missing something here? Is there any other debugging steps I
should take? Any insights or help will be hugely appreciated.<br>
<br>
Thank you,<br>
Omid<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Powered by <a class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a>
Visit other Kitware open-source projects at <a class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>
Please keep messages on-topic and check the ParaView Wiki at: <a class="moz-txt-link-freetext" href="http://paraview.org/Wiki/ParaView">http://paraview.org/Wiki/ParaView</a>
Search the list archives at: <a class="moz-txt-link-freetext" href="http://markmail.org/search/?q=ParaView">http://markmail.org/search/?q=ParaView</a>
Follow this link to subscribe/unsubscribe:
<a class="moz-txt-link-freetext" href="http://public.kitware.com/mailman/listinfo/paraview">http://public.kitware.com/mailman/listinfo/paraview</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Omid Mahabadi, Ph.D.
Geomechanica, Inc.
<a class="moz-txt-link-freetext" href="http://www.geomechanica.com/">http://www.geomechanica.com/</a>
Tel : +1-647-478-9767
Cell: +1-416-824-2408
</pre>
</body>
</html>