View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004233Slicer4Core: Base Codepublic2016-07-12 23:512017-06-15 14:02
ReporterJasCB Assigned Topieper  
PrioritynormalSeveritycrashReproducibilityalways
Status resolvedResolutionfixed 
Product Version 
Target VersionFixed in Version 
Summary0004233: Slicer is crashy on the cloud
Description

Hi, I have received instructions from my IT colleagues about how to report this but as a clinician I have little IT background myself, hopefully this makes sense :) My IT colleague suspects Slicer is crashing the specific data I'm testing it with.

I have been running Slicer on my institution's HPC cloud in order to teach courses on it, but it's been misbehaving lately.

Thank you so much for your help.

Steps To Reproduce

Please find below two instances in which I got it to crash:

79 280 281 282 283 284 285 286 287 288 289 290 291 292
Models saved to scene file /tmp/Slicer/CIBBA_AxHfACfEAAJHbA.mrml

Switch to module: "VolumeRendering"
Warning: In /home/kitware/Dashboards/Package/Slicer-450/Libs/MRML/Core/vtkObserverManager.cxx, line 131
vtkObserverManager (0x8870b00): The same object is already observed with the same priority. The observation is kept as is.Warning: In /home/kitware/Dashboards/Package/Slicer-450/Libs/MRML/Core/vtkObserverManager.cxx, line 131
vtkObserverManager (0x8870b00): The same object is already observed with the same priority. The observation is kept as is.error: [/opt/slicer/./bin/SlicerApp-real] exit abnormally - Report the problem.
~ $ ^C
~ $ ^C
~ $

6 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292
Models saved to scene file /tmp/Slicer/DBGF_AxHfHfIAAAafJA.mrml

Switch to module: "VolumeRendering"
Warning: In /home/kitware/Dashboards/Package/Slicer-450/Libs/MRML/Core/vtkObserverManager.cxx, line 131
vtkObserverManager (0x7b366e0): The same object is already observed with the same priority. The observation is kept as is.Warning: In /home/kitware/Dashboards/Package/Slicer-450/Libs/MRML/Core/vtkObserverManager.cxx, line 131
vtkObserverManager (0x7b366e0): The same object is already observed with the same priority. The observation is kept as is.error: [/opt/slicer/./bin/SlicerApp-real] exit abnormally - Report the problem.
~ $

Both times were by using the sample dataset MRHead, I did paint -> watershed -> make model -> volume rendering -> crop, which was fine. then when I clicked close scene it crashed

Additional Information

An observation I have made is that it seems as though it's the process of performing several operations that seems to crash it, more so than what the operations actually are.

Cheers!

Jas

TagsNo tags attached.

Activities

pieper

pieper

2016-09-20 10:59

administrator   ~0014096

Can you add information about exactly what data you were using and what steps led to the crash? Ideally if you could include step-by-step instructions to replicate the issue using publicly available data (for example by starting from one of the datasets in the SampleData module).
lassoan

lassoan

2017-06-13 08:45

developer   ~0014801

We've fixed a couple of scene close crashes in the nightly. Would it be possible to update the docker image/create a new one with a recent nightly build?
lassoan

lassoan

2017-06-15 14:02

developer   ~0014876

Several scene close issues has been fixed. We have not heard back from the reporter, so we assume that the fixes were enough.

Issue History

Date Modified Username Field Change
2016-07-12 23:51 JasCB New Issue
2016-07-12 23:51 JasCB Status new => assigned
2016-07-12 23:51 JasCB Assigned To => jcfr
2016-09-20 10:54 pieper Assigned To jcfr => pieper
2016-09-20 10:59 pieper Note Added: 0014096
2016-09-20 10:59 pieper Status assigned => feedback
2017-06-13 08:45 lassoan Note Added: 0014801
2017-06-15 14:02 lassoan Status feedback => resolved
2017-06-15 14:02 lassoan Resolution open => fixed
2017-06-15 14:02 lassoan Note Added: 0014876