[Paraview] ParaView 3.12.0 hanging

Thu Feb 23 18:36:54 EST 2012

Hi Burlen,

I applied your patch before recompiling.

This problem is only happen on versions >= 3.12 that are on 
headless/gpuless servers.

I'm guessing that it's a problem with offscreen rendering on the server. 
Or it could be a similar subtle bug in vtkSocket... I'll keep looking.

Thanks for your help,

Goodwin

On 24/02/2012 03:04, Burlen Loring wrote:
> Hi Goodwin,
>
> Did you also apply the patch on the server side? Again it may not help,
> but without it if there is an error during recv the call would silently
> restart and you'd never know about the error. I had a similar deadlock
> as you do here with version 3.10 on our Cray XE which is how I noticed
> the bug in vtkSocket.
>
> Burlen
>
> On 02/23/2012 06:05 AM, Goodwin Lawlor wrote:
>> On 22/02/2012 17:54, Utkarsh Ayachit wrote:
>>> Goodwin,
>>>
>>> Thanks for the update.
>>>
>>> Utkarsh
>>
>> Here's the backtrace on the remote server:
>>
>> The server has no GPU and uses OSMesa.
>>
>> It's stuck in vtkSocket::Receive() too! (so is the client)
>>
>>
>> #0 0x00007ffff72868a2 in recv () from /lib64/libpthread.so.0
>> #1 0x000000000470af5a in vtkSocket::Receive (this=0x6aabcb0,
>> data=0x7fffffffc20c, length=4, readFully=1)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/VTK/Common/vtkSocket.cxx:605
>>
>> #2 0x0000000002a7dfdf in vtkSocketCommunicator::ReceiveTagged
>> (this=0x6aabdf0, data=0x7fffffffc48c, wordSize=4, numWords=1, tag=16,
>> logName=0x6eb17d8 "Int32") at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/VTK/Parallel/vtkSocketCommunicator.cxx:810
>>
>> #3 0x0000000002a7a4b1 in vtkSocketCommunicator::ReceiveVoidArray
>> (this=0x6aabdf0, data=0x7fffffffc48c, length=1, type=6,
>> remoteProcessId=1, tag=16)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/VTK/Parallel/vtkSocketCommunicator.cxx:366
>>
>> #4 0x0000000001548700 in vtkCommunicator::Receive (this=0x6aabdf0,
>> data=0x7fffffffc48c, maxlength=1, remoteHandle=1, tag=16)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/VTK/Parallel/vtkCommunicator.h:203
>>
>> #5 0x0000000002a7f5a8 in vtkSocketCommunicator::Barrier (this=0x6aabdf0)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/VTK/Parallel/vtkSocketCommunicator.cxx:1104
>>
>> #6 0x000000000186ddaa in vtkMultiProcessController::Barrier
>> (this=0x68d0980)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/VTK/Parallel/vtkMultiProcessController.h:1338
>>
>> #7 0x000000000186adba in
>> vtkPVSynchronizedRenderWindows::HandleEndRender (this=0x6ad4080)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/ParaViewCore/ClientServerCore/vtkPVSynchronizedRenderWindows.cxx:839
>>
>> #8 0x000000000186f88e in
>> vtkPVSynchronizedRenderWindows::vtkObserver::Execute (this=0x6ae4460,
>> ocaller=0x6b27dc0, eventId=4)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/ParaViewCore/ClientServerCore/vtkPVSynchronizedRenderWindows.cxx:223
>>
>> #9 0x00000000046bcba9 in vtkSubjectHelper::InvokeEvent
>> (this=0x6b4ccb0, event=4, callData=0x0, self=0x6b27dc0)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/VTK/Common/vtkObject.cxx:602
>>
>> #10 0x00000000046bd0b5 in vtkObject::InvokeEvent (this=0x6b27dc0,
>> event=4, callData=0x0)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/VTK/Common/vtkObject.cxx:770
>>
>> #11 0x00000000030a2ba6 in vtkRenderWindow::Render (this=0x6b27dc0)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/VTK/Rendering/vtkRenderWindow.cxx:444
>>
>> #12 0x00000000018569d4 in vtkPVRenderView::Render (this=0x6ae5630,
>> interactive=true, skip_rendering=false)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/ParaViewCore/ClientServerCore/vtkPVRenderView.cxx:937
>>
>> #13 0x0000000001856181 in vtkPVRenderView::InteractiveRender
>> (this=0x6ae5630)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/ParaViewCore/ClientServerCore/vtkPVRenderView.cxx:759
>>
>> #14 0x0000000001777924 in vtkPVRenderViewCommand (arlu=0x63a0090,
>> ob=0x6ae5630, method=0x6ae6fd9 "InteractiveRender", msg=...,
>> resultStream=...)
>> at
>> /home/ec2-user/vol_30GB/builds/ParaView3.14.0-rc2/ParaViewCore/ClientServerCore/vtkPVRenderViewClientServer.cxx:264
>>
>> #15 0x0000000002427474 in
>> vtkClientServerInterpreter::ProcessCommandInvoke (this=0x63a0090,
>> css=..., midx=0)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:379
>>
>> #16 0x0000000002426b73 in
>> vtkClientServerInterpreter::ProcessOneMessage (this=0x63a0090,
>> css=..., message=0)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:214
>>
>> #17 0x0000000002426a11 in vtkClientServerInterpreter::ProcessStream
>> (this=0x63a0090, css=...)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:183
>>
>> #18 0x0000000001703e94 in vtkPVSessionCore::ExecuteStreamInternal
>> (this=0x63a2ba0, stream=..., ignore_errors=false)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/ParaViewCore/ServerImplementation/vtkPVSessionCore.cxx:636
>>
>> #19 0x0000000001703c93 in vtkPVSessionCore::ExecuteStream
>> (this=0x63a2ba0, location=21, stream=..., ignore_errors=false)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/ParaViewCore/ServerImplementation/vtkPVSessionCore.cxx:606#20
>> 0x0000000001700b47 in vtkPVSessionBase::ExecuteStream (this=0x63a2cc0,
>> location=21, stream=..., ignore_errors=false)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/ParaViewCore/ServerImplementation/vtkPVSessionBase.cxx:173
>>
>> #21 0x000000000170e6c6 in vtkPVSessionServer::OnClientServerMessageRMI
>> (this=0x63a2cc0, message=0x6acd530, message_length=16)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/ParaViewCore/ServerImplementation/vtkPVSessionServer.cxx:508
>>
>> #22 0x000000000170ca2c in (anonymous namespace)::RMICallback
>> (localArg=0x63a2cc0, remoteArg=0x6acd530, remoteArgLength=16)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/ParaViewCore/ServerImplementation/vtkPVSessionServer.cxx:56
>>
>> #23 0x00000000029f5dd7 in vtkMultiProcessController::ProcessRMI
>> (this=0x6aabcf0, remoteProcessId=1, arg=0x6acd530, argLength=16,
>> rmiTag=55625)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/VTK/Parallel/vtkMultiProcessController.cxx:655
>>
>> #24 0x00000000029f59a4 in vtkMultiProcessController::ProcessRMIs
>> (this=0x6aabcf0, reportErrors=0, dont_loop=1)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/VTK/Parallel/vtkMultiProcessController.cxx:602
>>
>> #25 0x0000000001892815 in
>> vtkTCPNetworkAccessManager::ProcessEventsInternal (this=0x63981c0,
>> timeout_msecs=0, do_processing=true)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx:256
>>
>> #26 0x00000000018923b0 in vtkTCPNetworkAccessManager::ProcessEvents
>> (this=0x63981c0, timeout_msecs=0)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/ParaViewCore/ClientServerCore/vtkTCPNetworkAccessManager.cxx:153
>>
>> #27 0x000000000143633c in RealMain (argc=1, argv=0x7fffffffe478,
>> type=vtkProcessModule::PROCESS_SERVER)
>> at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/CommandLineExecutables/pvserver_common.h:67
>>
>> #28 0x00000000014363d3 in main (argc=1, argv=0x7fffffffe478) at
>> /home/ec2-user/vol_30GB/codes/ParaView-3.14.0-RC2/CommandLineExecutables/pvserver.cxx:21
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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
>

-- 
Bioengineering Research Group
School of Mechanical and Materials Engineering
University College Dublin, Ireland
http://www.bioengineering-research.com