[Paraview] PV2.6 Crashes

Thu Feb 1 10:27:50 EST 2007

I'm using the released PV2.6 and seeing some strange crashes.

I'm using the Windows Version you guys compiled for the pvclient, and
running the PVServer on a linux Cluster.  I compiled the server myself with
OSMesa (6.4.2) & MPI (OpenMPI 1.1.1-1)support, and i'm running it on
multiple processors (the number doesn't matter).  When I compiled it, I
seeded CMake with the following cache:
BUILD_DOCUMENTATION:BOOL=OFF
BUILD_EXAMPLES:BOOL=OFF
BUILD_SHARED_LIBS:BOOL=ON
BUILD_TESTING:BOOL=OFF

CMAKE_BUILD_TYPE:STRING=Release
CMAKE_CXX_COMPILER:FILEPATH=/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1
/bin/mpicxx
CMAKE_C_COMPILER:FILEPATH=/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1/bin/mpicc
CMAKE_INSTALL_PREFIX:PATH=/viz/home/rhand/local/pv-2.4
//Path to a file.
MPI_INCLUDE_PATH:PATH=/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1/include
MPI_LIBRARY:FILEPATH=/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1/lib64/libmpi.so
OPENGL_INCLUDE_DIR:PATH=/viz/home/rhand/local/include
OPENGL_gl_LIBRARY:FILEPATH=/viz/home/rhand/local/lib/libVTKMesaGL.so
OPENGL_glu_LIBRARY:FILEPATH=/viz/home/rhand/local/lib/libVTKMesaGLU.so
OPENGL_xmesa_INCLUDE_DIR:PATH=/viz/home/rhand/local/include
OSMESA_INCLUDE_DIR:PATH=/viz/home/rhand/local/include
OSMESA_LIBRARY:FILEPATH=/viz/home/rhand/local/lib/libOSVTKMesa.so

VTK_OPENGL_HAS_OSMESA:BOOL=ON

VTK_USE_64BIT_IDS:BOOL=ON
VTK_USE_MPI:BOOL=ON

VTK_USE_RPATH:BOOL=OFF

Problem #1:
If I load an ImageData dataset (VTI) and then attempt to use the Clip filter
on it, it crashes every time.  Also, I get no ghost cells so when I extract
an isosurface the process boundaries are clearly visible.  I place the Clip
Filter at roughly 45-degrees (eyeballed, not much precision) so that it
gives me the lower-left half of the data, and when it crashes I get a trace
like the following:

Connected to client
Process id: 0 >> ERROR: In
/viz/home/rhand/src/pv-2.6/comp/PV/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
line 497
vtkXOpenGLRenderWindow (0x5362f50): bad X server connection. DISPLAY=Process
id: 0 >> ERROR: In
/viz/home/rhand/src/pv-2.6/comp/PV/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
line 319
Signal:11 info.si_errno:0(Success) si_code:1(SEGV_MAPERR)
Failing at addr:0x10
[0] func:/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1/lib64/libopal.so.0
[0x2a9bf15dd5]
[1] func:/lib64/tls/libpthread.so.0 [0x3dd910c430]
[2] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN22vtkXOpenGLRenderWindow13CreateAWindowEv+0x216)
[0x2a984e13f6]
[3] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN22vtkXOpenGLRenderWindow16WindowInitializeEv+0x12)
[0x2a984e21d2]
[4] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN22vtkXOpenGLRenderWindow5StartEv+0xd)
[0x2a984e249d]
[5] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN15vtkRenderWindow14DoStereoRenderEv+0x10)
[0x2a98452160]
[6] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN15vtkRenderWindow10DoFDRenderEv+0x36b)
[0x2a984520fb]
[7] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN15vtkRenderWindow10DoAARenderEv+0x46b)
[0x2a98451d3b]
[8] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN15vtkRenderWindow6RenderEv+0x149)
[0x2a98451439]
[9] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN22vtkXOpenGLRenderWindow6RenderEv+0x1c)
[0x2a984e437c]
[10] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN25vtkOpenGLExtensionManager20ReadOpenGLExtensionsEv+0xc0)
[0x2a984ab450]
[11] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN25vtkOpenGLExtensionManager6UpdateEv+0x52)
[0x2a984aac12]
[12] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN32vtkPVOpenGLExtensionsInformation14CopyFromObjectEP9vtkObject+0xf9)
[0x2a955b0bf9]
[13] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN17vtkSelfConnection17GatherInformationEjP16vtkPVInformation17vtkClientServerID+0x83)
[0x2a955dc163]
[14] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN20vtkMPISelfConnection17GatherInformationEjP16vtkPVInformation17vtkClientServerID+0x64)
[0x2a9559e684]
[15] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN19vtkClientConnection15SendInformationER21vtkClientServerStream+0x1d5)
[0x2a9558ff65]
[16] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_Z39vtkClientConnectionGatherInformationRMIPvS_ii+0x48)
[0x2a955900b8]
[17] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkParallel.so.pv2.6(_ZN25vtkMultiProcessController10ProcessRMIEiPvii+0x9e)
[0x2a9707ef6e]
[18] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkParallel.so.pv2.6(_ZN25vtkMultiProcessController11ProcessRMIsEii+0xa0)
[0x2a9707f3b0]
[19] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN19vtkRemoteConnection20ProcessCommunicationEv+0x14)
[0x2a955d9fb4]
[20] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN33vtkProcessModuleConnectionManager18MonitorConnectionsEm+0x2d9)
[0x2a955d81d9]
[21] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN16vtkProcessModule11StartServerEm+0x76)
[0x2a955cb676]
[22] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN16vtkProcessModule5StartEiPPc+0x24d)
[0x2a955ce8cd]
[23] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVFilters.so(_ZN9vtkPVMain3RunEP12vtkPVOptions+0x7b)
[0x2a95857b7b]
[24] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/pvserver-real(main+0xc2)
[0x402482]
[25] func:/lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x3dd881c3fb]
[26] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/pvserver-real(__gxx_personality_v0+0x5a)
[0x40232a]
*** End of error message ***

If I load the same ImageData Dataset & apply the D3 filter, then attempt to
use the Clip filter, it works.  I have alot of rendering artifacts (I think
due to the Structured->Unstructured conversion) and it takes ALOT of memory,
but it works.

Problem #2:
I find myself having to toggle the "Immediate Mode" option after pretty much
every filter to maintain performance.  It seems to be dropping back to
slower (safer?) methods every time I make a significant rendering change,
and if I simply toggle the Immediate Mode  On & then back off, my
performance improves 10-fold.  Anyone else experiencing this?
-- 
----------------------------------------
Randall Hand
Visualization Scientist
ERDC MSRC-ITL
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/paraview/attachments/20070201/b961488c/attachment.html