After opening or creating binary images, mitk crashes when it comes to rendering the respective images. Internally, getting the lookup table for binary images, a zero pointer is returned within mitk::ImageVtkMapper2D::ApplyLookuptable. The problem might have been solved on behalf of T8165.
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
Tobias could you please check if this bug is still present? There were some rendering fixes during the last time.
Comment Actions
Currently, the binary image rendering does not make mitk crash anymore, so this bug will be closed for now.