Dear All!
I have a few issues with getting paraview v3.10.0/v3.10.1 running without
getting a segmentation fault just after the logo window appears and the Qt
window builds up. This happens only for the time being if I am using the
following settings:
+ MPI support enabled (using openMPI v1.4.3)
+ OS MESA enabled (v7.9.2), using MESA for all openGL includes and libraries.
+ QT v4.6.3
+ Python 2.7.1
+ CMake 2.8.4
The system is Linux x86_64 based on SLES10.
The segmentation fault does not appear if I leave OpenMPI out of the loop (ie
building without MPI support). Using the standard OpenGL libraries (disabling
full CPU rendering and using GPU rendering instead, i.e. VTK_HAS_OSMESA=OFF)
and MPI support does not produce the segmentation fault either.
I have been backing off the CMAKE_BUILD_TYPE=Release and switched to
CMAKE_BUILD_TYPE=Debug, the recompiled paraview from scratch, alas without any
success. I still get the same segmentation fault. I have tried also with the
system compiler (gcc 4.1.2) and newer compiler versions (gcc v4.5.1 and 4.6.0),
the result still being the same.
I have included a backtrace from gdb in order to check where the segmentation
fault is produced and it looks like this happens in vtkOpenGLRenderWindow.cxx
on line 241.
#0 0x0000000000b14f90 in ?? ()
#1 0x00002aaab68640b7 in vtkOpenGLRenderWindow::OpenGLInit (this=0x1506230) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/VTK/Rendering/vtkOpenGLRenderWindow.cxx:241
#2 0x00002aaab68c18c1 in vtkXOpenGLRenderWindow::WindowInitialize
(this=0x1506230) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1043
#3 0x00002aaab68c1907 in vtkXOpenGLRenderWindow::Initialize (this=0x1506230)
at
/scratch/fal/COMPILE/ParaView-3.10.1/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1052
#4 0x00002aaab68c1dbb in vtkXOpenGLRenderWindow::Start (this=0x1506230) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1185
#5 0x00002aaab677ae0d in vtkRenderWindow::DoStereoRender (this=0x1506230) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/VTK/Rendering/vtkRenderWindow.cxx:687
#6 0x00002aaab677adde in vtkRenderWindow::DoFDRender (this=0x1506230) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/VTK/Rendering/vtkRenderWindow.cxx:676
#7 0x00002aaab677a873 in vtkRenderWindow::DoAARender (this=0x1506230) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/VTK/Rendering/vtkRenderWindow.cxx:563
#8 0x00002aaab6779e22 in vtkRenderWindow::Render (this=0x1506230) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/VTK/Rendering/vtkRenderWindow.cxx:376
#9 0x00002aaab68c4755 in vtkXOpenGLRenderWindow::Render (this=0x1506230) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1845
#10 0x00002aaaaddf7a2d in vtkPVRenderView::Render (this=0x146e140,
interactive=false, skip_rendering=false) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/Servers/Filters/vtkPVRenderView.cxx:752
#11 0x00002aaaaddf72b7 in vtkPVRenderView::StillRender (this=0x146e140) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/Servers/Filters/vtkPVRenderView.cxx:592
#12 0x00002aaaad75837e in vtkPVRenderViewCommand (arlu=0xcafc80, ob=0x146e140,
method=0x126d499 "StillRender", msg=@0x7fffffffb1c0, resultStream=@0xce66a0)
at
/scratch/fal/COMPILE/ParaView-3.10.1/build/Servers/Filters/vtkPVRenderViewClientServer.cxx:238
#13 0x00002aaab61794aa in vtkClientServerInterpreter::ProcessCommandInvoke
(this=0xcafc80, css=@0x7fffffffb560, midx=0)
at
/scratch/fal/COMPILE/ParaView-3.10.1/src/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:379
#14 0x00002aaab6178bc9 in vtkClientServerInterpreter::ProcessOneMessage
(this=0xcafc80, css=@0x7fffffffb560, message=0)
at
/scratch/fal/COMPILE/ParaView-3.10.1/src/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:214
#15 0x00002aaab6178a63 in vtkClientServerInterpreter::ProcessStream
(this=0xcafc80, css=@0x7fffffffb560)
at
/scratch/fal/COMPILE/ParaView-3.10.1/src/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:183
#16 0x00002aaab119786d in vtkSelfConnection::ProcessStreamLocally
(this=0x1443880, stream=@0x7fffffffb560) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/Servers/Common/vtkSelfConnection.cxx:118
#17 0x00002aaab1197829 in vtkSelfConnection::SendStreamToClient
(this=0x1443880, stream=@0x7fffffffb560) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/Servers/Common/vtkSelfConnection.cxx:111
#18 0x00002aaab1117f95 in vtkProcessModuleConnection::SendStream
(this=0x1443880, servers=21, stream=@0x7fffffffb560)
at
/scratch/fal/COMPILE/ParaView-3.10.1/src/Servers/Common/vtkProcessModuleConnection.cxx:241
#19 0x00002aaab111b486 in vtkProcessModuleConnectionManager::SendStream
(this=0x12247b0, connectionID=5, serverFlags=21, stream=@0x7fffffffb560,
reset=1)
at
/scratch/fal/COMPILE/ParaView-3.10.1/src/Servers/Common/vtkProcessModuleConnectionManager.cxx:541
#20 0x00002aaab1124e0a in vtkProcessModule::SendStream (this=0xca5610,
connectionID=5, server=21, stream=@0x7fffffffb560, resetStream=1)
at
/scratch/fal/COMPILE/ParaView-3.10.1/src/Servers/Common/vtkProcessModule.cxx:919
#21 0x00002aaaad2d2a10 in vtkSMViewProxy::StillRender (this=0x1405280) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/Servers/ServerManager/vtkSMViewProxy.cxx:136
#22 0x00002aaaab695a20 in pqView::forceRender (this=0x14d1860) at
/scratch/fal/COMPILE/ParaView-3.10.1/src/Qt/Core/pqView.cxx:199
#23 0x00002aaaab6a97b3 in pqView::qt_metacall (this=0x14d1860,
_c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x7fffffffb6f0) at
/scratch/fal/COMPILE/ParaView-3.10.1/build/Qt/Core/moc_pqView.cxx:121
#24 0x00002aaaab6a447b in pqRenderViewBase::qt_metacall (this=0x14d1860,
_c=QMetaObject::InvokeMetaMethod, _id=21, _a=0x7fffffffb6f0)
at
/scratch/fal/COMPILE/ParaView-3.10.1/build/Qt/Core/moc_pqRenderViewBase.cxx:74
#25 0x00002aaaab6a40bf in pqRenderView::qt_metacall (this=0x14d1860,
_c=QMetaObject::InvokeMetaMethod, _id=21, _a=0x7fffffffb6f0)
at
/scratch/fal/COMPILE/ParaView-3.10.1/build/Qt/Core/moc_pqRenderView.cxx:95
#26 0x00002aaab0cddcbf in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from
/opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libQtCore.so.4
#27 0x00002aaab0cdb78a in QObject::event(QEvent*) () from
/opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libQtCore.so.4
#28 0x00002aaaafa4dc4f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libQtGui.so.4
#29 0x00002aaaafa52e62 in QApplication::notify(QObject*, QEvent*) () from
/opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libQtGui.so.4
#30 0x00002aaab0ccad44 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libQtCore.so.4
#31 0x00002aaab0cf77de in ?? () from
/opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libQtCore.so.4
#32 0x00002aaab0cf5224 in ?? () from
/opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libQtCore.so.4
#33 0x00002aaabbbbefea in g_main_context_dispatch () from
/opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libglib-2.0.so.0
#34 0x00002aaabbbc2075 in ?? () from
/opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libglib-2.0.so.0
#35 0x00002aaabbbc259e in g_main_context_iteration () from
/opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libglib-2.0.so.0
#36 0x00002aaab0cf5565 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libQtCore.so.4
#37 0x00002aaaafaf886f in ?? () from
/opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libQtGui.so.4
#38 0x00002aaab0ccc57c in
QCoreApplication::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/opt/paraview/MESA/paraview-3.10.1/lib/paraview-3.10/libQtCore.so.4
#39 0x0000000000408e76 in pqparaviewInitializer::Initialize
(this=0x7fffffffc2d0, argc=1, argv=0x7fffffffc428)
at
/scratch/fal/COMPILE/ParaView-3.10.1/build/Applications/ParaView/pqparaviewInitializer.cxx:143
#40 0x0000000000408593 in main (argc=1, argv=0x7fffffffc428) at
/scratch/fal/COMPILE/ParaView-3.10.1/build/Applications/ParaView/paraview_main.cxx:76
I have been successfully compiling and installing on the same computer paraview
3.8.1 without any issues, using similar settings:
+ QT v4.6.2
+ Python v2.7
+ MESA 7.7.1
+ openMPI 1.4.3
The software rendering is working like a charm and the reason why looking
forward to using paraview 3.10.X is the enhanced support for parallel
rendering. I am quite sure I am doing everything right but it would be great to
know if someone would be pointing me towards a fix for this issue.
For information, I am using a compute cluster which does not have dedicated GPU
hardware and, mainly for this reason, I am relying heavily on CPU based,
parallel rendering for performing postprocessing. Paraview v3.8.1 has been
running on this cluster for the last 4 months now without given any trouble.
Best regards,
Frank Albina
---
Mail frank.alb...@sauber-motorsport.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 ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
