View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003554Slicer4Module CropVolumepublic2014-01-10 14:472015-03-04 12:23
Reporterffranconeri Assigned Tofedorov  
PrioritynormalSeverityblockReproducibilityalways
Status closedResolutionunable to reproduce 
Product VersionSlicer 4.3.0 
Target VersionFixed in Version 
Summary0003554: Slicer has caught an internal error - bad allocation
Description

After selecting the module "Crop Volume" when pressing the button "Crop!" the message box "Slicer has caught an internal error" is displayed. The message detail is: Exception thrown in event: bad allocation (see the attached printout).

TagsNo tags attached.

Relationships

related to 0003947 closednicole Repeated crop volume freezes Slicer 

Activities

2014-01-10 14:47

 

BadAllocationError-OnCropCommand.png (525,181 bytes)
fedorov

fedorov

2014-01-10 15:46

developer   ~0010505

I am unable to reproduce this problem with the details you provided.

I tested on Windows, with the current stable release. I used ROI created from volume rendering (based on your screenshot). I made ROI extend beyond the volume area. I tested with MRHead dataset.

Can you try if you can reproduce with the current stable release? (looks like you use an older version of Slicer)
fedorov

fedorov

2015-03-04 12:23

developer   ~0012967

please test after the commit in issue 0003947 and reopen if needed

Issue History

Date Modified Username Field Change
2014-01-10 14:47 ffranconeri New Issue
2014-01-10 14:47 ffranconeri Status new => assigned
2014-01-10 14:47 ffranconeri Assigned To => fedorov
2014-01-10 14:47 ffranconeri File Added: BadAllocationError-OnCropCommand.png
2014-01-10 15:46 fedorov Note Added: 0010505
2014-01-10 15:46 fedorov Status assigned => feedback
2015-03-04 12:22 fedorov Relationship added related to 0003947
2015-03-04 12:23 fedorov Note Added: 0012967
2015-03-04 12:23 fedorov Status feedback => closed
2015-03-04 12:23 fedorov Resolution open => unable to reproduce