issue is probably related to image with full dynamic range and datatype "unsigned short". Sample image "T10_defect_s2.nrrd" has intensities in the full range 0-65535, the other two do not. Loading that image when others are already present seems to trigger the crash.

Unable to reproduce on Ubuntu 13.10 using Slicer r22924.

No crash for me loading these on the nightly build from 2014-03-03 on mac.

@Dominik could you see it it still crashes for you on the nightly?

Just checked: selecting all three and dragging them into my debug build of today's code caused a crash:
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000121489000

VM Regions Near 0x121489000:
MALLOC_LARGE 0000000121449000-0000000121489000 [ 256K] rw-/rwx SM=PRV
-->
__TEXT 00000001214c6000-00000001214e9000 [ 140K] r-x/rwx SM=COW /Users/USER//.dylib

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libMRMLCore.dylib 0x000000010ca9dce8 void vtkImageBimodalAnalysisExecute<int>(vtkImageBimodalAnalysis, vtkImageData, int, vtkImageData, float) + 776 (vtkImageBimodalAnalysis.cxx:113)
1 libMRMLCore.dylib 0x000000010ca9b4f2 vtkImageBimodalAnalysis::ExecuteData(vtkDataObject) + 1762 (vtkImageBimodalAnalysis.cxx:274)
2 libvtkFiltering.5.10.dylib 0x000000011c7dff32 vtkSource::ProcessRequest(vtkInformation*, vtkInformationVector, vtkInformationVector) + 5682 (vtkSource.cxx:670)
3 libvtkFiltering.5.10.dylib 0x000000011c57b7a4 vtkExecutive::CallAlgorithm(vtkInformation, int, vtkInformationVector, vtkInformationVector) + 164 (vtkExecutive.cxx:747)
4 libvtkFiltering.5.10.dylib 0x000000011c55c60a vtkDemandDrivenPipeline::ExecuteData(vtkInformation, vtkInformationVector, vtkInformationVector) + 154 (vtkDemandDrivenPipeline.cxx:506)
5 libvtkFiltering.5.10.dylib 0x000000011c55b8bb vtkDemandDrivenPipeline::ProcessRequest(vtkInformation, vtkInformationVector, vtkInformationVector) + 1515 (vtkDemandDrivenPipeline.cxx:279)
6 libvtkFiltering.5.10.dylib 0x000000011c7e75b2 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation, vtkInformationVector*, vtkInformationVector) + 2146 (vtkStreamingDemandDrivenPipeline.cxx:276)
7 libvtkFiltering.5.10.dylib 0x000000011c55c333 vtkDemandDrivenPipeline::UpdateData(int) + 1091 (vtkDemandDrivenPipeline.cxx:449)
8 libvtkFiltering.5.10.dylib 0x000000011c7e7880 vtkStreamingDemandDrivenPipeline::Update(int) + 240 (vtkStreamingDemandDrivenPipeline.cxx:326)
9 libvtkFiltering.5.10.dylib 0x000000011c7dcc31 vtkSource::Update() + 81 (vtkSource.cxx:136)
10 libMRMLCore.dylib 0x000000010cc78369 vtkMRMLScalarVolumeDisplayNode::CalculateAutoLevels() + 1833 (vtkMRMLScalarVolumeDisplayNode.cxx:745)
11 libMRMLCore.dylib 0x000000010cc77991 vtkMRMLScalarVolumeDisplayNode::ProcessMRMLEvents(vtkObject, unsigned long, void) + 257 (vtkMRMLScalarVolumeDisplayNode.cxx:404)
12 libMRMLCore.dylib 0x000000010cc21c8b vtkMRMLNode::MRMLCallback(vtkObject, unsigned long, void, void) + 1035 (vtkMRMLNode.cxx:850)
13 libvtkCommon.5.10.dylib 0x000000011ceb6bf4 vtkCallbackCommand::Execute(vtkObject, unsigned long, void) + 84 (vtkCallbackCommand.cxx:43)
14 libMRMLCore.dylib 0x000000010ca9156f vtkEventBroker::InvokeObservation(vtkObservation, unsigned long, void) + 255 (vtkEventBroker.cxx:843)
15 libMRMLCore.dylib 0x000000010ca90ddc vtkEventBroker::ProcessEvent(vtkObservation, vtkObject, unsigned long, void) + 188 (vtkEventBroker.cxx:689)
16 libMRMLCore.dylib 0x000000010ca91ecb vtkEventBroker::Callback(vtkObject, unsigned long, void, void) + 507 (vtkEventBroker.cxx:915)
17 libvtkCommon.5.10.dylib 0x000000011ceb6bf4 vtkCallbackCommand::Execute(vtkObject, unsigned long, void) + 84 (vtkCallbackCommand.cxx:43)
18 libvtkCommon.5.10.dylib 0x000000011cfc259c vtkSubjectHelper::InvokeEvent(unsigned long, void, vtkObject) + 2460 (vtkObject.cxx:620)
19 libvtkCommon.5.10.dylib 0x000000011cfc2b42 vtkObject::InvokeEvent(unsigned long, void) + 66 (vtkObject.cxx:789)
20 libvtkCommon.5.10.dylib 0x000000011cfc2d22 vtkObject::Modified() + 66 (vtkObject.cxx:856)
21 libMRMLCLI.dylib 0x000000010c9a5114 vtkMRMLNode::Modified() + 52 (vtkMRMLNode.h:363)
22 libMRMLCore.dylib 0x000000010cd4dd12 vtkMRMLVolumeDisplayNode::SetInputImageData(vtkImageData) + 82 (vtkMRMLVolumeDisplayNode.cxx:109)
23 libMRMLCore.dylib 0x000000010cc7510e vtkMRMLScalarVolumeDisplayNode::SetInputImageData(vtkImageData) + 142 (vtkMRMLScalarVolumeDisplayNode.cxx:160)
24 libMRMLCore.dylib 0x000000010cd5a764 vtkMRMLVolumeNode::SetAndObserveImageData(vtkImageData) + 212 (vtkMRMLVolumeNode.cxx:704)
25 libMRMLCore.dylib 0x000000010cd4226b vtkMRMLVolumeArchetypeStorageNode::ReadDataInternal(vtkMRMLNode) + 13531 (vtkMRMLVolumeArchetypeStorageNode.cxx:438)

Interesting - there have been a number of crashes reported in vtkImageBimodalAnalysisExecute.

Looks like that code hasn't changed since 2008 (according to git blame) so I wonder what else has changed.

Actually just eyeballing the code now I see how it could be wrong. Line 113 can be accessing beyond the end of the array since width is 5 and max could be at the end of the histogram. I suggest putting in a check if x+k >= max0.

@Jc this one is assigned to you - do you want to fix this or should I?

@Steve: Would appreciate if you could take this one :) Thanks

Fixed in r22942. @Dominik if you could confirm with tomorrows nightly build and close the bug that would be great.

Tested on a debug build, no crash.

Confirmed by Dominik on the nightly build.