Page MenuHomePhabricator

Segmentation crashes when mixing up 3D and 4D images
Closed, ResolvedPublic

Description

  • Load T:\temp\basti\3D.pic
  • Load T:\temp\basti\4D.pic
  • Create a new Segmentation for 3D pic.
  • Reinit on 3D pic. (now you can segment nicely)
  • Reinit on 4D pic. A warning will occur "Please perform a reinit on the segmentation image"
  • Selected Patient Image: "4D". A warning will occur "the selected patient image does not match with the selected segmentation"
  • Select Patient Image: "3D". The warning disappears.
  • Try to segment something

--> Crash!

Event Timeline

If you do it the other way around, MITK produces a memory leak:

  • Load T:\temp\basti\tv_filtered.pic
  • Load T:\temp\basti\4D.pic
  • Create Segmentation of 4D.pic (without reiniting on this image)
  • segment around: You can watch your memory filling up rapidly with each segmentation action.

Currently it seems that the Image-Geometry and the Segmentation-Geometry are checked to be equal! Otherwise there is a warning. Additionally, A warning is shown to indicate that a reinit is necessary, when the image-combobx has changed (?).

I assume, that this "reinint"-Warning can be adapted to fix this bug. It should check the current world geometry and the image-Geometry to be equal.

Alternatively, the segmentation tools should include a check, if the segmented are is within the geometry of the image.

This bug is relevant for the upcoming release

[393e6f]: Merge branch 'bug-16469-segmentationwarning'

Merged commits:

2013-11-27 14:59:41 Bastian Graser [18f136]
checking world-geometry with selected image and segmentation node geometry