being new to this program, I’m not sure where to send crash information, and what to send.
I have saved the main part of the ‘Send to Apple’ crash report, in a text file, if that is useful, and, of course, can save the whole ball of wax, if desirable?
We take crash reports seriously. The most important thing is to know is how to replicate the issue with public data, so please try to do that and file a bug report with all the details. If the crash is hard to reproduce, then yes, the crash info can help. Mostly it’s just the first chunk of 20-30 lines of the stack trace that’s important, but that may be hard to judge so posting it all can’t hurt (put it in a google drive or similar and link here if it’s really big).
The crash file is just 231 K, so I’ll attach it here… I had an ROI-limited 3D of head and C-spine up, from a CTA with 0.5 mm slices.
I was doing a ‘trim’ with scissors tool… hopefully not doing something dumb, but something dumb should tell me
The images are my own scans (what a mess… sigh…)
anyway, I attach the crash file in ,txt
If you wish to suggest other information, let me know… if the image files are needed, it would be nice to keep them kind of confidential
(Attachment DOING SCISSORS EDIT IN 3D Panel copy.txt is missing)
The system rejected the text file, it’s hard to make it an MP4
Do you use Wetransfer, for example?
Yes, any file transfer service is fine, like dropbox, google drive, onedrive, etc.
Are you using an M series mac by any chance? We’ve seen issues with random crashes there probably due to the on-the-fly translation so clicking the report to Apple option might help. I’ve been able to replicate this issue with the SampleData and in this case there doesn’t appear to be much we can do in Slicer since it appears to be an OS / chip level issue.
OK… I’m using an old MacMini with Mojave 10.14.6
I’ll try wetransfer to
you should have a notification and link coming to you
I’m not sure you can send to the discourse mail like that with wetransfer (I don’t think anyone gets that email). If you can make a public download link that will be better.
let’s see if this works
Yes, that worked. This is the key information indicating that something has gone wrong internal to the scissors implementation.
The other key information that’s needed is how to reproduce the crash so it can be debugged and fixed. Does this happen consistently for you and if so, what steps lead up to it?
0 libvtkCommon-9.1.1.dylib 0x000000011c721fdb vtkCellLinks::BuildLinks(vtkDataSet*) + 891 1 libvtkCommon-9.1.1.dylib 0x000000011c8b2670 vtkPolyData::BuildLinks(int) + 160 2 libvtkFilters-9.1.1.dylib 0x000000011bd78dce vtkPolyDataNormals::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1614 3 libvtkCommon-9.1.1.dylib 0x000000011c694015 vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 69 4 libvtkCommon-9.1.1.dylib 0x000000011c68ed5d vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 61 5 libvtkCommon-9.1.1.dylib 0x000000011c689198 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 104 6 libvtkCommon-9.1.1.dylib 0x000000011c68e51d vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1437 7 libvtkCommon-9.1.1.dylib 0x000000011c6d2990 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 848 8 libvtkCommon-9.1.1.dylib 0x000000011c68a439 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 297 9 libvtkCommon-9.1.1.dylib 0x000000011c68e33d vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 957 10 libvtkCommon-9.1.1.dylib 0x000000011c6d2990 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 848 11 libvtkCommon-9.1.1.dylib 0x000000011c6d2f8b vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 283 12 libqSlicerSegmentationsEditorEffects.dylib 0x000000013855eadb qSlicerSegmentEditorScissorsEffectPrivate::updateBrushStencil(qMRMLWidget*) + 203 13 libqSlicerSegmentationsEditorEffects.dylib 0x000000013855ee39 qSlicerSegmentEditorScissorsEffectPrivate::paintApply(qMRMLWidget*) + 137 14 libqSlicerSegmentationsEditorEffects.dylib 0x0000000138562bb0 qSlicerSegmentEditorScissorsEffect::processInteractionEvents(vtkRenderWindowInteractor*, unsigned long, qMRMLWidget*) + 448 15 libqSlicerSegmentationsModuleWidgets.dylib 0x000000013841b75b qMRMLSegmentEditorWidget::processEvents(vtkObject*, unsigned long, void*, void*) + 619 16 libvtkCommon-9.1.1.dylib 0x000000011ce6dff1 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 33 17
hello…good to know that it’s pointing to something … I’m not in very good shape today (CSF leak(s)) but I’ll try to light up the slicer, and reproduce the problem.
the files are my scans, but i can also try with a sample set.
Can you confirm that your mac mini has an intel chip? I.e. is it before the M1 versions were introduced? I ask because I’ve only seen this particular crash on Apple silicon and not with intel.
yes, Steve, it’s an i5 2.3 GHz.
late 2012, Mojave 10.14.6
I’m having trouble getting to approximately the same 'state’s, being as lost as I am in the application. : -(
i can’t seem to get to a point where scissors work on the 3d image, or anywhere, for that matter… it’s frustrating, that a tool that is so obviously powerful, and graphically ‘pleasing’, is so driven by some “other appreciation” of User Experience (user experience is something that i have real-world experience with, in both 'consumer’s and ‘engineering’ fields, with extremely complex instruments )… i really can’t spend months to accomplish even seemingly-simple tasks, in the midst of attempting to get to some understanding of a combination of CSF leak, apparent VBI of unknown aetiology, but both apparently connected to Cervical spine (truly a mess on MR and CT!)
I’ll keep plugging away at it…
btw, is there any simple way to ‘translate’ the 3d object? there are ‘buttons’ to rock it, or spin it, but no readily-apparent mouse mode to move the object in the viewport’s x/y? Surely it’s just one more ‘beginner missing something obvious’!
the entire 'segmentation thing’s is also killing me…sorry, folks…
it’s a beautiful Sunday morning, first day of Advent, Christmas markets open … maybe time for Glühwein instead of C-spine!
Thanks for reporting back @Lohi - the fact that you get the same stack trace on an intel mac as I see on the M2 mac, but isn’t seen on windows/linux, indicates perhaps it’s something to do with the Apple compilers or something else to be determined. Hopefully with more debugging we’ll get to the bottom of it. Please try these instructions for capturing the program state so you can share it if a crash occurs.
And yes, Slicer is a UI/UX minefield. Just so you know, we have limited developer resources so we draw an arbitrary line and say that any hardware over 5 years old should be considered unsupported, so your 10 year old mac mini is way out of spec for current Slicer. Still, we’d like it to work anyway and it’s helpful for debugging, but it may never be usable with the latest releases. A newer computer might save you some frustration.
Regarding translating the object (or for Slicer, the camera) on a mac with a trackpad you press shift and then use the trackpad click-and-drag motion. A three-button mouse is highly recommended if you are doing a lot of interactive visualization and segmentation.
i do understand about “resource limitations”…
I’ve not ‘updated’ my Mac mini, because later versions had more restrictions on expansion, and it seems that Apple has made the newest ones kind of 'what you buy is. what you’really stuck witch’s, as far as RAM, although i guess drives can be changed. I’m thinking seriously about going to Linux, at some point, but my ‘newer’ i7 Mac still has enough performance for most of what zip do.
i thought that i had tried every combination of keys to get translation, but ‘shift’, maybe not.
i noticed some kind of debug thing in preferences, turned it on.