View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002184Slicer4Module Editorpublic2012-06-11 07:092012-08-20 09:58
Reportervikasrs Assigned Topieper  
PrioritynormalSeveritycrashReproducibilityrandom
Status closedResolutionfixed 
Product VersionSlicer 4.1.0 
Target VersionSlicer 4.2.0Fixed in VersionSlicer 4.2.0 
Summary0002184: Crash - Identify and Remove Islands effect
Description

Application crashes after performing the following actions in editor module:
Apply Threshold -> IdentifyIslands -> RemoveIslands

The crash occurs either when Apply IdentifyIsland or Apply RemoveIsland effect is performed.

Sometimes the above pipeline works. Repeat the above steps to reproduce the crash.

TagsNo tags attached.

Relationships

related to 0001832 closedpieper add try/catch around render calls and event processing 

Activities

jcfr

jcfr

2012-06-15 10:55

administrator   ~0004842

From Vikas - June 15, 2012:

Hi Steve,

I am using Slicer 4.1.0. I tested the following pipeline on Windows, Mac and Linux platforms.

  1. Load the Slicer4Minute/greyscale.nrrd volume
  2. In Editor - Apply Threshold - Range 80 to 320
  3. Apply IdentifyIslandsEffect with label 1 selected
  4. Apply RemoveIslandsEffect with label 1 selected

Repeat steps 2-4.

The application was stable and did not crash in Mac and Linux.
I tested on two different machines running Windows 7. In both machines the applications crashes after 5 to 6 iterations of steps 2-4.
pieper

pieper

2012-06-16 11:57

administrator   ~0004845

Since this only happened on the 32 bit build, it's likely that the issue is memory related. Issue 1832 proposes a way to at least detect and gracefully fail in these situations.
jcfr

jcfr

2012-06-16 11:59

administrator   ~0004846

From Vikas - June 15 2012:

I tested it on 32bit Windows 7 and 64 bit Windows 7. It crashed in both cases.
pieper

pieper

2012-08-09 10:41

administrator   ~0005531

Fixed in revision 20738
pieper

pieper

2012-08-09 11:02

administrator   ~0005532

Update: actually fixed in 20739
pieper

pieper

2012-08-20 09:58

administrator   ~0005597

Not sure if original poster is still active. The issue is fixed - re-open if issue recurs.

Issue History

Date Modified Username Field Change
2012-06-11 07:09 vikasrs New Issue
2012-06-11 07:09 vikasrs Status new => assigned
2012-06-11 07:09 vikasrs Assigned To => pieper
2012-06-11 07:42 jcfr Target Version => Slicer 4.2.0 - Sept 1st 2012
2012-06-15 10:55 jcfr Note Added: 0004842
2012-06-16 11:55 pieper Relationship added related to 0001832
2012-06-16 11:57 pieper Note Added: 0004845
2012-06-16 11:59 jcfr Note Added: 0004846
2012-08-09 10:41 pieper Note Added: 0005531
2012-08-09 10:42 pieper Status assigned => feedback
2012-08-09 10:42 pieper Resolution open => fixed
2012-08-09 11:02 pieper Note Added: 0005532
2012-08-20 09:58 pieper Note Added: 0005597
2012-08-20 09:58 pieper Status feedback => closed
2012-08-20 09:58 pieper Fixed in Version => Slicer 4.2.0 - Feature freeze Sept 1st 2012