MantisBT - ParaView
View Issue Details
0015763ParaView(No Category)public2015-10-08 19:262015-12-16 17:11
Alan Scott 
Utkarsh Ayachit 
urgentcrashhave not tried
closedfixed 
4.4 
5.05.0 
Sandia
incorrect functionality
0015763: Crash remote server
PV 4.4.0 has a bad crash remote server. This one appears hard to replicate. Here is a way to replicate it every time. Note to myself - Dataset is under arne's directory.

* Blow away your .config files. (Not sure of --dr works, I assume it would.)
* Linux, 4.4.0, remote server (16 processes). (Note to myself - Chama, 1 node)
* Open deep_target.g.100.[000-099]. Apply.
* Right click on the cylendar. Rotate the dataset UP about 60 degrees, so that you mainly see the yellow box, but can still see the blue stuff inside of the box.
* Right click on the yellow box. This will work.
* Left click somewhere in the gray background, bringing down the menu.
* Right click on the blue stuff in the box.

Seg faults on the server side.



ERROR: In /projects/viz/paraview/src/ParaView/4.4.0/ParaView4/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 875
vtkSocketCommunicator (0x1601800): Tag mismatch: got 1, expecting 22222.

ERROR: In /projects/viz/paraview/src/ParaView/4.4.0/ParaView4/ParaViewCore/ClientServerCore/Rendering/vtkPVSynchronizedRenderWindows.cxx, line 1125
vtkPVSynchronizedRenderWindows (0xf37d60): Mismatch is render windows on different processes. Aborting for debugging purposes.

[chama32:14983] *** Process received signal ***
[chama32:14983] Signal: Aborted (6)
[chama32:14983] Signal code: (-6)
[chama32:14983] [ 0] /lib64/libpthread.so.0(+0xf710) [0x2aaab1fbb710]
[chama32:14983] [ 1] /lib64/libc.so.6(gsignal+0x35) [0x2aaab3e2e625]
[chama32:14983] [ 2] /lib64/libc.so.6(abort+0x175) [0x2aaab3e2fe05]
[chama32:14983] [ 3] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVClientServerCoreRendering-pv4.4.so.1(_ZN30vtkPVSynchronizedRenderWindows19LoadWindowAndLayoutEP15vtkRenderWindowR21vtkMultiProcessStream+0x3d1) [0x2aaab8e2a781]
[chama32:14983] [ 4] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVClientServerCoreRendering-pv4.4.so.1(_ZN30vtkPVSynchronizedRenderWindows15RootStartRenderEP15vtkRenderWindow+0x54) [0x2aaab8e29f04]
[chama32:14983] [ 5] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVClientServerCoreRendering-pv4.4.so.1(_ZN30vtkPVSynchronizedRenderWindows17HandleStartRenderEP15vtkRenderWindow+0x3b) [0x2aaab8e29b3b]
[chama32:14983] [ 6] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVClientServerCoreRendering-pv4.4.so.1(+0xea48d) [0x2aaab8e2c48d]
[chama32:14983] [ 7] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkCommonCore-pv4.4.so.1(+0x2bd799) [0x2aaab28d6799]
[chama32:14983] [ 8] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkCommonCore-pv4.4.so.1(_ZN9vtkObject11InvokeEventEmPv+0x12) [0x2aaab28d63e2]
[chama32:14983] [ 9] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkRenderingCore-pv4.4.so.1(_ZN15vtkRenderWindow6RenderEv+0x69) [0x2aaaad2066d9]
[chama32:14983] [10] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkRenderingCore-pv4.4.so.1(_ZN19vtkHardwareSelector14CaptureBuffersEv+0xf7) [0x2aaaad1b83a7]
[chama32:14983] [11] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVClientServerCoreRendering-pv4.4.so.1(_ZN21vtkPVHardwareSelector13PrepareSelectEv+0x63) [0x2aaab8dfd443]
[chama32:14983] [12] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVClientServerCoreRendering-pv4.4.so.1(_ZN21vtkPVHardwareSelector6SelectEPi+0x15) [0x2aaab8dfd2e5]
[chama32:14983] [13] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVClientServerCoreRendering-pv4.4.so.1(_ZN15vtkPVRenderView6SelectEiPi+0x72) [0x2aaab8e1ae72]
[chama32:14983] [14] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVClientServerCoreRendering-pv4.4.so.1(_ZN15vtkPVRenderView11SelectCellsEPi+0xe) [0x2aaab8e1adfe]
[chama32:14983] [15] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVServerManagerApplication-pv4.4.so.1(_Z22vtkPVRenderViewCommandP26vtkClientServerInterpreterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x54ed) [0x2aaaab75235d]
[chama32:14983] [16] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkClientServer-pv4.4.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkObjectBaseS1_RK21vtkClientServerStreamRS4_+0xe5) [0x2aaaaf733f85]
[chama32:14983] [17] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkClientServer-pv4.4.so.1(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkClientServerStreami+0x131) [0x2aaaaf733851]
[chama32:14983] [18] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkClientServer-pv4.4.so.1(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClientServerStreami+0x18d) [0x2aaaaf7328fd]
[chama32:14983] [19] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkClientServer-pv4.4.so.1(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientServerStream+0x29) [0x2aaaaf733e69]
[chama32:14983] [20] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVServerImplementationCore-pv4.4.so.1(_ZN16vtkPVSessionCore21ExecuteStreamInternalERK21vtkClientServerStreamb+0xab) [0x2aaaac6b564b]
[chama32:14983] [21] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVServerImplementationCore-pv4.4.so.1(_ZN16vtkPVSessionCore13ExecuteStreamEjRK21vtkClientServerStreamb+0x66) [0x2aaaac6b3356]
[chama32:14983] [22] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVServerImplementationCore-pv4.4.so.1(_ZN16vtkPVSessionBase13ExecuteStreamEjRK21vtkClientServerStreamb+0x30) [0x2aaaac6b13b0]
[chama32:14983] [23] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVServerImplementationCore-pv4.4.so.1(_ZN18vtkPVSessionServer24OnClientServerMessageRMIEPvi+0x2c3) [0x2aaaac6bbd73]
[chama32:14983] [24] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVServerImplementationCore-pv4.4.so.1(+0x47aa6) [0x2aaaac6bbaa6]
[chama32:14983] [25] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkParallelCore-pv4.4.so.1(_ZN25vtkMultiProcessController10ProcessRMIEiPvii+0xa8) [0x2aaab04606d8]
[chama32:14983] [26] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkParallelCore-pv4.4.so.1(_ZN25vtkMultiProcessController11ProcessRMIsEii+0x13f) [0x2aaab04601ef]
[chama32:14983] [27] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVClientServerCoreCore-pv4.4.so.1(_ZN26vtkTCPNetworkAccessManager21ProcessEventsInternalEmb+0x202) [0x2aaaac9cde32]
[chama32:14983] [28] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/libvtkPVClientServerCoreCore-pv4.4.so.1(_ZN26vtkTCPNetworkAccessManager13ProcessEventsEm+0xb) [0x2aaaac9cdc2b]
[chama32:14983] [29] /projects/viz/paraview/ParaView/4.4.0-Mesa/Linux-chama-x86_64/lib/paraview-4.4/pvserver(main+0x1f4) [0x404014]
[chama32:14983] *** End of error message ***

No tags attached.
Issue History
2015-10-08 19:26Alan ScottNew Issue
2015-10-08 19:27Alan ScottTarget Version => 5.0
2015-10-08 19:35Alan ScottDescription Updatedbug_revision_view_page.php?rev_id=1328#r1328
2015-10-08 19:46Alan ScottPrioritynormal => urgent
2015-10-08 19:46Alan ScottSeverityminor => crash
2015-10-09 10:17Utkarsh AyachitNote Added: 0035269
2015-10-09 10:19Utkarsh AyachitNote Added: 0035270
2015-10-09 20:31Alan ScottNote Added: 0035271
2015-10-13 17:02Utkarsh AyachitNote Added: 0035280
2015-10-13 17:02Utkarsh AyachitStatusbacklog => customer review
2015-10-13 17:02Utkarsh AyachitFixed in Version => git-master
2015-10-13 17:02Utkarsh AyachitResolutionopen => fixed
2015-10-13 17:02Utkarsh AyachitAssigned To => Utkarsh Ayachit
2015-10-28 09:29Utkarsh AyachitFixed in Versiongit-master => 5.0
2015-12-01 20:27Alan ScottNote Added: 0035510
2015-12-01 20:27Alan ScottStatuscustomer review => todo
2015-12-08 08:33Utkarsh AyachitNote Added: 0035520
2015-12-08 09:55Utkarsh AyachitNote Added: 0035521
2015-12-08 09:55Utkarsh AyachitStatustodo => gatekeeper review
2015-12-09 04:03Utkarsh AyachitStatusgatekeeper review => customer review
2015-12-16 17:11Alan ScottNote Added: 0035582
2015-12-16 17:11Alan ScottStatuscustomer review => closed

Notes
(0035269)
Utkarsh Ayachit   
2015-10-09 10:17   
A simple way to reproduce this bug:

+ Start ParaView with remote rendering enabled (I was using 2 ranks, but may fail with 1 rank too).
+ Simply click in the empty Render View more than once. You'll get the reported errors.
(0035270)
Utkarsh Ayachit   
2015-10-09 10:19   
VTK MR: https://gitlab.kitware.com/vtk/vtk/merge_requests/753 [^]
(0035271)
Alan Scott   
2015-10-09 20:31   
Note - I have tested the fix in production code, and it does fix the issue. Redsky, 8 nodes, deep_target along with Utkarsh's shorter version above.
(0035280)
Utkarsh Ayachit   
2015-10-13 17:02   
Fixes now merged in `master`.
(0035510)
Alan Scott   
2015-12-01 20:27   
Sorry, this one isn't fixed.

* From what I can tell, the "short" Utkarsh fix now is correct.
* Following the directions below, I still get the same error.

This one must be fixed for 5.0. Ask me for the dataset, if needed.
(0035520)
Utkarsh Ayachit   
2015-12-08 08:33   
Another way to reproduce the bug:

+ Start ParaView with remote rendering enabled (I was using 2 ranks, but may fail with 1 rank too).
+ Create Sphere, Apply.
+ Simply click in the empty parts of the Render View more than *twice*. You'll get the reported errors.
(0035521)
Utkarsh Ayachit   
2015-12-08 09:55   
This should fix it:
https://gitlab.kitware.com/paraview/paraview/merge_requests/507 [^]
(0035582)
Alan Scott   
2015-12-16 17:11   
Yep, that appears to have fixed it. Thanks.

Tested Linux, remote server (redsky, 2 nodes), 5.0.0-RC1.

Tested my procedure, also Utkarsh's.