Thank you for clarification! Indeed, this is an important remark! Seems that we checked on an outdated website for minimum compiler version before fixing this.

Pushed new branch T25979-FixImageStatisticsContainerCompilerError.

In T24754#138569, @eisenman wrote:

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.

By the way: Linking works fine if OpenIGTLink is built separately and specified in CMake via EXTERNAL_OpenIGTLink_DIR. But the link libraries property is also empty in this case.

We figured out that the exported target OpenIGTLink does not have any linked libraries. Thank you @kislinsk for your help!

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.

We noticed a changed behavior compared to previous workbench release:

• Load data as described above (topmost visible data set has 3 time steps, data set below has 10 time steps)
• Move time slider to the end

--> Slider can be moved to a 12th time step

Pushed new branch T25237-FixCompilerErrorAndCleanupIplImageRemoval.

Changing the return type of ImageToOpenCVImageFilter::GetOpenCVImage() leads to a compiler error in test method "ConvertIplImageForthAndBack" of test driver "mitkOpenCVMitkConversionTest".

I already downgraded to 15.7.6, sorry! But I still have the error prompt in case that helps. Maybe @aguilera still has 15.8.0 installed and can test the proposed solution?

I can confirm an internal compiler error when building with Visual Studio 15.8.0 and 15.8.1 (I updated today). Python, Numpy, and SimpleITK were not enabled in my case.

What is the status? Ready to be merged in the alpha branch?

This issue does not occur anymore!

Pushed new branch T25179-FixCompilerError.

Could you please provide a data set in order to reproduce this bug (maybe from MITK-Data)?

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 :)

Pushed new branch T24763-ResponsiveLayoutOfWelcomeScreen.

It appears on Linux as well!

In T24755#131187, @kislinsk wrote:

@eisenman Did or do you work on this?

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 tested on Windows 7 and Ubuntu 15.04. 2D Fast Marching Segmentation Tool is working without any warnings.

Pushed new branch T24355-SetDefaultFocusToBasicInformationTab-v2.

This occurs again in v2018.04-alpha branch.

Pushed new branch T24726-FixLinuxCompileIssues.

Pushed new branch T19348-SupportOpenCV3.

Pushed new branch T24212-VTKDebugLeaksInUltrasoundSupport-Integration.

There's the issue, that removing a created USDevice doesn't lead to a destructor call of the respective instance. I'm expecting the device instance to be deleted. So I checked the reference count of the USDevice instance after removing it: After unregistering the device from the micro service, the reference count is 2.

Debug leaks also occur in MITK v2016.11.

The error "ServiceRegistrationBase object invalid" was solved in T24505.