The crash was fixed in the latest VolumeResliceDriver:

https://github.com/SlicerIGT/VolumeResliceDriver/commit/aa55ded8bd9a56f431fde117dfe9412f79f6c3c6

It was due to division by zero. When VolumeResliceDriver calculates a normal vector for volume reslicing, it uses a vector that connects two points of the annotation ruler. When the length of the ruler becomes zero (by step 6 described above), the previous code tried to calculate a normal vector by dividing a vector (0, 0, 0) by 0.

Although the crash can be avoided by using arbitrary vector e.g. (1, 0, 0), such an arbitrary vector cause a change of reslicing plane, when the Visual Offset becomes zero.

I think I fixed the issue by adding:

if (!sliceNode)
{
return;
}

to the beginning of UpdateSlice in vtkSlicerVolumeResliceDriverLogic (line 517 for me).

Could you test it, and let me know if it works for you.

Thanks.

No actually what I said is wrong.

I thought it worked because when reslicing to Axial, Sagittal or Coronal, you can go to 0 without crash, but if you choose a different reslicing (transverse, in plane, etc...) then it crashes when going to 0.

I will try to update VolumeResliceDriver to see if it works for me.

Thanks.

It works for me, it's not crashing anymore.
However, as you said, orientation became wrong at 0.

A solution could be, save the previous orientation, and use it if both points are at same position (vector 0,0,0).
How does it sound to you ?

VisuaLine is now compatible with latest OpenIGTLink version, and preserve the orientation even if length is 0.

Closing resolved issues that have not been updated in more than 3 months