Page MenuHomePhabricator

Volume Visualization crashes with some CT images
Closed, ResolvedPublic

Description

  • Open MITK-Data/3D+t-Heart
  • Switch on volume visualization 💣
  • Crash 💥

Revisions and Commits

rMITK MITK
Restricted Differential Revision
Restricted Differential Revision
Restricted Differential Revision

Event Timeline

kislinsk triaged this task as High priority.May 9 2018, 2:05 PM
kislinsk created this task.

Segmentation fault occurs in vtkAOSDataArrayTemplate::GetTypedComponent(vtkIdType tupleIdx, int comp) after accessing the buffer[0].
Crash only occurs with the DICOM 3D+t image which also causes trouble in T24767 and T24766. Seems to work with all other 3d+t images in MITKData. Volume visualization works for the image if it is exported to .nrrd first.

We found out that volume visualization works as expected when following the described steps:

  • Close rendering display
  • Open MITK-Data/3D+t-Heart (rendering display is opened automatically)
  • Switch on volume visualization
  • No crash :)

We couldn't find out the difference between the initial rendering display and the second rendering display so far.

The issue still occurs on both Windows and Linux systems. The transfer function widget seems to be initialized correctly. The last MITK method called before diving into VTK internals mentioned above is VtkMapper::MitkRenderVolumetricGeometry.

I remove this task from the beta backlog. If there's a strong interest in having this fixed in the upcoming release, someone has to fix it this week and assign the MITK (2018-04) tag again.

We found out that volume visualization works as expected when following the described steps:

  • Close rendering display
  • Open MITK-Data/3D+t-Heart (rendering display is opened automatically)
  • Switch on volume visualization
  • No crash :)

We couldn't find out the difference between the initial rendering display and the second rendering display so far.

Cannot reproduce this behavior with the current master branch anymore. Now it always crashes.

This issue still occurs. Following previous finding still holds true: Volume visualization works for the image if it is exported to nrrd first and then loaded as nrrd.

Seems that the pixel type is not set properly:
Show details lists "Channel: Unnamed [scalar], PixelType: scalar" for the nrrd file and "Channel: Unnamed [], PixelType: " for the DICOM file.

Could this be the reason for the access violation later on?

I couldn't reproduce this bug in the latest Release installer on Windows. However, there is no volume visualization shown at all (no matter which timestep or which histogram I select).
If the crash does not occur anymore on Ubuntu etc. we can resolve the crash bug.

I mentioned the general problem with 4D data and visualization here: T28274

kahl added a revision: Restricted Differential Revision.Nov 24 2021, 1:49 PM