MantisBT - ParaView
View Issue Details
0012842ParaView(No Category)public2012-01-05 19:482012-02-08 17:24
Burlen 
Bob O'Bara 
normalminorhave not tried
closedno change required 
3.12 
3.14 
TBD
crash
0012842: segfault in vtkVolumeRayCastSpaceLeapingImageFilter
Hi,

In 3.12 when volume rendering on image data I'm experiencing segfaults in vtkVolumeRayCastSpaceLeapingImageFilter in vtkVolumeRayCastSpaceLeapingImageFilterMinMaxExecute. The issue seems to be that vtkImageData::ComputeIncrements relies on active scalars being set. However, for use with ParaView I don't think this can be guaranteed. for instance how would an object that produces multiple arrays, eg a reader, correctly set active scalars?

A quick fix is below, the real fix probably is quite a bit more involved.

--- ParaView-3.12.0-base/VTK/VolumeRendering/vtkVolumeRayCastSpaceLeapingImageFilter.cxx 2011-11-08 12:56:45.000000000 -0800
+++ ParaView-3.12.0/VTK/VolumeRendering/vtkVolumeRayCastSpaceLeapingImageFilter.cxx 2012-01-05 16:34:06.217415840 -0800
@@ -801,6 +801,10 @@
     return;
     }
 
+ // FIXME --- this keeps things running smoothly when active scalars
+ // are not set but modifies the input
+ inData[0][0]->GetPointData()->SetScalars(this->GetCurrentScalars())
+
   const int components = this->GetCurrentScalars()->GetNumberOfComponents();
   const unsigned int nComponents = (this->GetIndependentComponents()) ? components : 1;
No tags attached.
Issue History
2012-01-05 19:48BurlenNew Issue
2012-01-13 09:51Utkarsh AyachitNote Added: 0027934
2012-01-13 09:51Utkarsh AyachitStatusbacklog => gatekeeper review
2012-01-13 09:51Utkarsh AyachitFixed in Version => git-master
2012-01-13 09:51Utkarsh AyachitResolutionopen => no change required
2012-01-13 09:51Utkarsh AyachitAssigned To => Bob O'Bara
2012-01-20 14:20Utkarsh AyachitStatusgatekeeper review => customer review
2012-01-20 14:20Utkarsh AyachitNote Added: 0027953
2012-02-08 17:21Utkarsh AyachitFixed in Versiongit-master => 3.14
2012-02-08 17:24Utkarsh AyachitStatuscustomer review => closed
2012-02-08 17:24Utkarsh AyachitNote Added: 0028119

Notes
(0027934)
Utkarsh Ayachit   
2012-01-13 09:51   
I believe this issue has already been fixed in git-master. Please reopen if you're still running into problems.
(0027953)
Utkarsh Ayachit   
2012-01-20 14:20   
merged in master (whenever applicable)
(0028119)
Utkarsh Ayachit   
2012-02-08 17:24   
Closing bugs sitting in "customer review" for a long time.