[Paraview] [EXTERNAL] Parallel paraview crashes when opening files
Scott, W Alan
wascott at sandia.gov
Mon Aug 19 13:23:57 EDT 2013
Georg,
This is a paraview bug. I have found it, and have a fix. I am just waiting for my cluster to come back online, so I can test. I will post a bug, and get Kitware to install the fix.
Alan
-----Original Message-----
From: Georg Hammerl [mailto:hammerl at lnm.mw.tum.de]
Sent: Friday, August 16, 2013 1:17 AM
To: Scott, W Alan
Cc: paraview at paraview.org
Subject: Re: [Paraview] [EXTERNAL] Parallel paraview crashes when opening files
Hello Alan,
sure, please feel free to use my files for writing a bug report.
And thanks again for having a look at the problem.
Georg
On 15/08/13 23:11, Scott, W Alan wrote:
> Georg,
> I am pretty sure this is a ParaView bug. It works local server, but doesn't work remote server. It also works with EnSight.
>
> Although I will poke at it for a while longer, mind if I write up a bug with Kitware, using your files? They show the bug well.
>
> Alan
>
>
>
>
> -----Original Message-----
> From: Georg Hammerl [mailto:hammerl at lnm.mw.tum.de]
> Sent: Wednesday, August 14, 2013 12:19 AM
> To: Scott, W Alan
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] [EXTERNAL] Parallel paraview crashes when
> opening files
>
> Hello Alan,
>
> attached are the files to reproduce the crashing of paraview.
>
> Thanks in advance for your help.
>
> Georg
>
>
> On 13/08/13 18:50, Scott, W Alan wrote:
>> Georg,
>> I don't know if I can figure it out, but send me the file again and I will try opening it up.
>> Alan
>>
>>
>> -----Original Message-----
>> From: Georg Hammerl [mailto:hammerl at lnm.mw.tum.de]
>> Sent: Tuesday, August 13, 2013 3:35 AM
>> To: paraview at paraview.org
>> Cc: Scott, W Alan
>> Subject: Re: [Paraview] [EXTERNAL] Parallel paraview crashes when
>> opening files
>>
>> Hello Alan,
>>
>> I know it is been a while but I ran into this issue again today and I had a look into the problem again. It seems to be related to the time steps. I use the ensight gold transient single-file format. When I remove all time stepping information (i.e. BEGIN TIME STEP and END TIME STEP and everything related to it in the case file) and only visualize one single time step everything works fine. I simply cannot figure out what is going wrong. I appreciate any help in solving this issue.
>>
>> Georg
>>
>>
>>
>> On 08/04/13 08:33, Georg Hammerl wrote:
>>> Alan,
>>>
>>> now I have compiled a debug version and I have attached with gdb to
>>> the server to find out where the segfault occurs.
>>> Here is the stacktrace:
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x00007f95c93bad40 in vtkIdList::GetId (this=0x0, i=0) at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/Core/vtkIdList.h:43
>>> 43 vtkIdType GetId(const vtkIdType i) {return this->Ids[i];};
>>> (gdb) bt
>>> #0 0x00007f95c93bad40 in vtkIdList::GetId (this=0x0, i=0) at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/Core/vtkIdList.
>>> h
>>> :43
>>> #1 0x00007f95c94a199a in vtkPEnSightReader::ReadVariableFiles
>>> (this=0x1b66d60, output=0x1b86050)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/VTKExtensions
>>> /
>>> Default/vtkPEnSightReader.cxx:1617
>>> #2 0x00007f95c9498fb2 in vtkPEnSightReader::RequestData
>>> (this=0x1b66d60, outputVector=0x1b6ab10)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/VTKExtensions
>>> /
>>> Default/vtkPEnSightReader.cxx:446
>>> #3 0x00007f95cfc2ee0f in
>>> vtkMultiBlockDataSetAlgorithm::ProcessRequest (this=0x1b66d60,
>>> request=0x1b86c40, inputVector=0x0, outputVector=0x1b6ab10)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkMultiBlockDataSetAlgorithm.cxx:88
>>> #4 0x00007f95cfc1b73f in vtkExecutive::CallAlgorithm
>>> (this=0x1b68c00, request=0x1b86c40, direction=1, inInfo=0x0, outInfo=0x1b6ab10)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkExecutive.cxx:744
>>> #5 0x00007f95cfc08ea7 in vtkDemandDrivenPipeline::ExecuteData
>>> (this=0x1b68c00, request=0x1b86c40, inInfo=0x0, outInfo=0x1b6ab10)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkDemandDrivenPipeline.cxx:498
>>> #6 0x00007f95cfbfe943 in vtkCompositeDataPipeline::ExecuteData
>>> (this=0x1b68c00, request=0x1b86c40, inInfoVec=0x0, outInfoVec=0x1b6ab10)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkCompositeDataPipeline.cxx:208
>>> #7 0x00007f95cfc085e7 in vtkDemandDrivenPipeline::ProcessRequest
>>> (this=0x1b68c00, request=0x1b86c40, inInfoVec=0x0, outInfoVec=0x1b6ab10)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkDemandDrivenPipeline.cxx:279
>>> #8 0x00007f95cfc3b188 in
>>> vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x1b68c00,
>>> request=0x1b86c40, inInfoVec=0x0, outInfoVec=0x1b6ab10)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkStreamingDemandDrivenPipeline.cxx:346
>>> #9 0x00007f95cfc08cf0 in vtkDemandDrivenPipeline::UpdateData
>>> (this=0x1b68c00, outputPort=0) at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkDemandDrivenPipeline.cxx:449
>>> #10 0x00007f95cfc3b3ea in vtkStreamingDemandDrivenPipeline::Update
>>> (this=0x1b68c00, port=0)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkStreamingDemandDrivenPipeline.cxx:399
>>> #11 0x00007f95cfbf70a6 in vtkAlgorithm::Update (this=0x1b66d60,
>>> port=0) at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkAlgorithm.cxx:1420
>>> #12 0x00007f95cfbf7071 in vtkAlgorithm::Update (this=0x1b66d60) at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkAlgorithm.cxx:1414
>>>
>>> #13 0x00007f95c8da0a44 in vtkGenericEnSightReader::RequestData
>>> (this=0x17e6a30, outputVector=0x1b67220) at
>>> /home/hammerl/programs_local/paraview_git/VTK/IO/EnSight/vtkGenericE
>>> n
>>> SightReader.cxx:229
>>> #14 0x00007f95cfc2ee0f in
>>> vtkMultiBlockDataSetAlgorithm::ProcessRequest (this=0x17e6a30,
>>> request=0x1b85730, inputVector=0x0, outputVector=0x1b67220)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkMultiBlockDataSetAlgorithm.cxx:88
>>> #15 0x00007f95cfc1b73f in vtkExecutive::CallAlgorithm
>>> (this=0x1b67110, request=0x1b85730, direction=1, inInfo=0x0, outInfo=0x1b67220)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkExecutive.cxx:744
>>> #16 0x00007f95cfc08ea7 in vtkDemandDrivenPipeline::ExecuteData
>>> (this=0x1b67110, request=0x1b85730, inInfo=0x0, outInfo=0x1b67220)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkDemandDrivenPipeline.cxx:498
>>> #17 0x00007f95cfbfe943 in vtkCompositeDataPipeline::ExecuteData
>>> (this=0x1b67110, request=0x1b85730, inInfoVec=0x0, outInfoVec=0x1b67220)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkCompositeDataPipeline.cxx:208
>>> #18 0x00007f95cfc085e7 in vtkDemandDrivenPipeline::ProcessRequest
>>> (this=0x1b67110, request=0x1b85730, inInfoVec=0x0, outInfoVec=0x1b67220)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkDemandDrivenPipeline.cxx:279
>>> #19 0x00007f95cfc3b188 in
>>> vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x1b67110,
>>> request=0x1b85730, inInfoVec=0x0, outInfoVec=0x1b67220)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkStreamingDemandDrivenPipeline.cxx:346
>>> #20 0x00007f95cfc00a4a in vtkCompositeDataPipeline::ForwardUpstream
>>> (this=0x1b82850, request=0x1b85730)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkCompositeDataPipeline.cxx:731
>>> #21 0x00007f95cfc08552 in vtkDemandDrivenPipeline::ProcessRequest
>>> (this=0x1b82850, request=0x1b85730, inInfoVec=0x1b83850,
>>> outInfoVec=0x1b82640)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkDemandDrivenPipeline.cxx:265 ---Type <return> to continue, or q
>>> <return> to quit---
>>> #22 0x00007f95cfc3b188 in
>>> vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x1b82850,
>>> request=0x1b85730, inInfoVec=0x1b83850, outInfoVec=0x1b82640)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkStreamingDemandDrivenPipeline.cxx:346
>>> #23 0x00007f95cfc08cf0 in vtkDemandDrivenPipeline::UpdateData
>>> (this=0x1b82850, outputPort=0) at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkDemandDrivenPipeline.cxx:449
>>> #24 0x00007f95cfc3b3ea in vtkStreamingDemandDrivenPipeline::Update
>>> (this=0x1b82850, port=0)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Common/ExecutionModel/
>>> v
>>> tkStreamingDemandDrivenPipeline.cxx:399
>>> #25 0x00007f95d54bb546 in vtkSISourceProxy::UpdatePipeline
>>> (this=0x18cdc50, port=0, time=0, doTime=true)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/ServerImpleme
>>> n
>>> tation/Core/vtkSISourceProxy.cxx:420
>>> #26 0x00007f95d641e317 in vtkSISourceProxyCommand (arlu=0x1375980,
>>> ob=0x18cdc50, method=0x1b82049 "UpdatePipeline", msg=...,
>>> resultStream=...)
>>> at
>>> /home/hammerl/programs_local/build_paraview_clean/Wrapping/ClientSer
>>> v
>>> er/vtkSISourceProxyClientServer.cxx:113
>>> #27 0x00007f95d136ee58 in
>>> vtkClientServerInterpreter::ProcessCommandInvoke (this=0x1375980,
>>> css=..., midx=0)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/ClientServerS
>>> t
>>> ream/vtkClientServerInterpreter.cxx:379
>>> #28 0x00007f95d136e591 in
>>> vtkClientServerInterpreter::ProcessOneMessage (this=0x1375980,
>>> css=..., message=0)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/ClientServerS
>>> t
>>> ream/vtkClientServerInterpreter.cxx:214
>>> #29 0x00007f95d136e42b in vtkClientServerInterpreter::ProcessStream
>>> (this=0x1375980, css=...)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/ClientServerS
>>> t
>>> ream/vtkClientServerInterpreter.cxx:183
>>> #30 0x00007f95d5476c37 in vtkPVSessionCore::ExecuteStreamInternal
>>> (this=0x1375910, stream=..., ignore_errors=false)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/ServerImpleme
>>> n
>>> tation/Core/vtkPVSessionCore.cxx:665
>>> #31 0x00007f95d5476a3a in vtkPVSessionCore::ExecuteStream
>>> (this=0x1375910, location=21, stream=..., ignore_errors=false)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/ServerImpleme
>>> n
>>> tation/Core/vtkPVSessionCore.cxx:635
>>> #32 0x00007f95d54733a2 in vtkPVSessionBase::ExecuteStream
>>> (this=0x1373f00, location=21, stream=..., ignore_errors=false)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/ServerImpleme
>>> n
>>> tation/Core/vtkPVSessionBase.cxx:173
>>> #33 0x00007f95d548309c in
>>> vtkPVSessionServer::OnClientServerMessageRMI
>>> (this=0x1373f00, message=0x1a39510, message_length=16)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/ServerImpleme
>>> n
>>> tation/Core/vtkPVSessionServer.cxx:510
>>> #34 0x00007f95d5481654 in (anonymous namespace)::RMICallback
>>> (localArg=0x1373f00, remoteArg=0x1a39510, remoteArgLength=16)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/ServerImpleme
>>> n
>>> tation/Core/vtkPVSessionServer.cxx:56
>>> #35 0x00007f95d043348a in vtkMultiProcessController::ProcessRMI
>>> (this=0x13fadb0, remoteProcessId=1, arg=0x1a39510, argLength=16,
>>> rmiTag=55625)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Parallel/Core/vtkMulti
>>> P
>>> rocessController.cxx:650
>>> #36 0x00007f95d0433020 in vtkMultiProcessController::ProcessRMIs
>>> (this=0x13fadb0, reportErrors=0, dont_loop=1)
>>> at
>>> /home/hammerl/programs_local/paraview_git/VTK/Parallel/Core/vtkMulti
>>> P
>>> rocessController.cxx:597
>>> #37 0x00007f95d5182276 in
>>> vtkTCPNetworkAccessManager::ProcessEventsInternal (this=0x12cf300,
>>> timeout_msecs=0, do_processing=true)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/ClientServerC
>>> o
>>> re/Core/vtkTCPNetworkAccessManager.cxx:268
>>> #38 0x00007f95d5181e14 in vtkTCPNetworkAccessManager::ProcessEvents
>>> (this=0x12cf300, timeout_msecs=0)
>>> at
>>> /home/hammerl/programs_local/paraview_git/ParaViewCore/ClientServerC
>>> o
>>> re/Core/vtkTCPNetworkAccessManager.cxx:165
>>> #39 0x0000000000401b83 in RealMain (argc=2, argv=0x7fff09f84c28,
>>> type=vtkProcessModule::PROCESS_SERVER) at
>>> /home/hammerl/programs_local/paraview_git/CommandLineExecutables/pvs
>>> e
>>> rver_common.h:90
>>> #40 0x0000000000401c35 in main (argc=2, argv=0x7fff09f84c28) at
>>> /home/hammerl/programs_local/paraview_git/CommandLineExecutables/pvs
>>> e
>>> rver.cxx:21
>>>
>>>
>>> I hope this helps to find the problem. Thanks in advance.
>>>
>>> Georg
>>>
>>>
>>>
>>>
>>> On 06/04/13 00:05, Scott, W Alan wrote:
>>>> By the way, this datasets kills my build also. I don't currently
>>>> have a debug build, so don't know where it died.
>>>>
>>>> Alan
>>>>
>>>> -----Original Message-----
>>>> From: paraview-bounces at paraview.org
>>>> [mailto:paraview-bounces at paraview.org] On Behalf Of Georg Hammerl
>>>> Sent: Friday, April 05, 2013 4:12 AM
>>>> To: paraview at paraview.org
>>>> Subject: [EXTERNAL] [Paraview] Parallel paraview crashes when
>>>> opening files
>>>>
>>>> Hello,
>>>>
>>>> I have compiled paraview from the git repo with MPI support on my
>>>> Linux 64-bit machine (openmpi 1.5.4). I can start Paraview with
>>>> multiple processors, but when I try to open one of my result files
>>>> I get the following error and Paraview is closed automatically:
>>>>
>>>> ERROR: In
>>>> /home/hammerl/programs_local/paraview_git/VTK/Parallel/Core/vtkSock
>>>> e
>>>> tCommunicator.cxx,
>>>>
>>>> line 812
>>>> vtkSocketCommunicator (0x2090510): Could not receive tag. 188969
>>>>
>>>> Attached is a file that can be used to reproduce the error.
>>>>
>>>> I appreciate any help to solve the problem.
>>>>
>>>> Cheers,
>>>>
>>>> Georg
>>>>
>>>> --
>>>> Dipl.-Ing. Georg Hammerl
>>>> Lehrstuhl für Numerische Mechanik
>>>> Technische Universität München
>>>> Boltzmannstrasse 15, D-85747 Garching b. München phone +49 89 289
>>>> 15237 fax +49 89 289 15301 hammerl at lnm.mw.tum.de
>>>> http://www.lnm.mw.tum.de
>>>>
>>>>
>>>>
>
> --
> Dipl.-Ing. Georg Hammerl
> Lehrstuhl für Numerische Mechanik
> Technische Universität München
> Boltzmannstrasse 15, D-85747 Garching b. München phone +49 89 289
> 15237 fax +49 89 289 15301 hammerl at lnm.mw.tum.de
> http://www.lnm.mw.tum.de
>
>
>
--
Dipl.-Ing. Georg Hammerl
Lehrstuhl für Numerische Mechanik
Technische Universität München
Boltzmannstrasse 15, D-85747 Garching b. München phone +49 89 289 15237 fax +49 89 289 15301 hammerl at lnm.mw.tum.de http://www.lnm.mw.tum.de
More information about the ParaView
mailing list