Chronological Thread 

< Chronological >      < Thread >

---

This crash appears to be fixed in v5.4 (release today).

Alan

On Tue, Jun 9, 2020 at 12:35 PM Allen Sanderson <allen@sci.utah.edu> wrote:
>
> Here is a bit more on the second seg fault I am getting
>
> Open SW Studio,
> Open the project,
> Select difference
> Click on Run Reconstruction.
>
> Here is the initial cost spew:
>
> There are 8071 / 8192 good points.
> Pmatrix - nnz = 96852
> Kmatrix - nnz = 2043081
> Lmatrix - nnz = 2236785
> 0
> 1
> #iterations: 2
> estimated error: 5.31546e-28
> 5.31546e-28
> Computing Wmatrix:
> Mean: 45.0914
> Total: 45.0914
> #iterations: 2
> estimated error: 5.31545e-28
> 5.31545e-28
> Computing Wmatrix:
> Mean: 42.454
> Total: 42.454
> ..
> Isosurface: /tmp/_dense-noQC.vtk
> Segmentation fault
>
>
> here is crash stack:
>
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0 libvtkCommonCore-8.2.1.dylib 0x00000001153f631d
> vtkGenericDataArray<vtkAOSDataArrayTemplate<float>,
> float>::GetComponent(long long, int) + 29
> 1 libvtkFiltersCore-8.2.1.dylib 0x0000000114a22976
> vtkGlyph3D::Execute(vtkDataSet*, vtkInformationVector*, vtkPolyData*,
> vtkDataArray*, vtkDataArray*) + 4710
> 2 libvtkFiltersCore-8.2.1.dylib 0x0000000114a21692
> vtkGlyph3D::RequestData(vtkInformation*, vtkInformationVector**,
> vtkInformationVector*) + 66
> 3 libvtkCommonExecutionModel-8.2.1.dylib 0x0000000114de88e5
> vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**,
> vtkInformationVector*) + 69
> 4 libvtkCommonExecutionModel-8.2.1.dylib 0x0000000114de319d
> vtkDemandDrivenPipeline::ExecuteData(vtkInformation*,
> vtkInformationVector**, vtkInformationVector*) + 61
> 5 libvtkCommonExecutionModel-8.2.1.dylib 0x0000000114dddc48
> vtkCompositeDataPipeline::ExecuteData(vtkInformation*,
> vtkInformationVector**, vtkInformationVector*) + 104
> 6 libvtkCommonExecutionModel-8.2.1.dylib 0x0000000114de291c
> vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*,
> vtkInformationVector**, vtkInformationVector*) + 1196
> 7 libvtkCommonExecutionModel-8.2.1.dylib 0x0000000114e0afde
> vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*,
> vtkInformationVector**, vtkInformationVector*) + 974
> 8 libvtkCommonExecutionModel-8.2.1.dylib 0x0000000114e0b44e
> vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 254
> 9 edu.utah.sci.shapeworks.studio 0x000000010e1ca815
> Viewer::display_object(QSharedPointer<DisplayObject>) + 2021
>
>
>
> Cheers,
>
> Allen
>
>
>
>
> On Jun 9, 2020, at 11:47 AM, Allen Sanderson <allen@sci.utah.edu> wrote:
>
> As Alan gave me a template for groups I am loading it and getting a hard
> crash with the following:
>
> Open SW Studio,
> Open the project,
> Immediately click on “Difference” SW studio will crash, seg fault.
>
> I can do this consistently.
>
> However, if I pause until the initial “reconstructed” surface comes up it
> does not crash.
>
> Also, being these are the initial “reconstructed” surfaces which are not
> very good. I ran the reconstruction using the defaults. During this process
> SW Studio crashed as well. I am running it again to see if it crashes
> consistently for this case. As Alan has the data being used I am including
> my groups.xml file so it can be duplicated.
>
>
>
> <groups.xml>
>
>
> Cheers,
>
> Allen
>
>
> Allen Sanderson
> SCI Institute
> University of Utah
>
>
>
>

---

• [shapeworks-dev-support] SW Studio seg fault, Allen Sanderson, 06/09/2020
  • Re: [shapeworks-dev-support] SW Studio seg fault, Allen Sanderson, 06/09/2020
    • Re: [shapeworks-dev-support] SW Studio seg fault, Alan Morris, 06/15/2020

---

Archive powered by MHonArc 2.6.18.