Can't reproduce with r20789 on Linux Ubuntu 10.04 LTS - the Lucid Lynx

I could not replicate this either (windows 7, visual studio 2008).

Does it happen on the nightly build?

It happens with the nightly build, but it seems that it's related to some of our own modules. I investigate it more and report here if there is any fix needed in the Slicer core.

After some more testing: it's not related to any custom modules, it's reproducible with the latest nightly build (Slicer-4.1.0-2012-08-18-win-amd64), but the crash may not happen always exactly the same way: sometimes it just hangs, sometimes it crashes almost immediately; sometimes you need to repeat the steps described above to reproduce the issue.

See a sample screencast (with the latest nightly build, without any custom extension, module, or setting, on Win7 64-bit):
http://screencast.com/t/wMoNWUijmOxf

Issue targeted for 4.2.0, re-target if it can't be addressed by sept 1st.

I could not reproduce this after several tries. Have you ever seen it on a debug build or only a release build?

I haven't tried it with debug build.

I just tried with a release build (latest nightly) and got the crash on the first try.

But was never able to get it to happen on a windows debug build.

Trying again on a mac debug build.

Okay - got the crash on mac with the following stack trace:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libvtkCommonPythonD.5.10.dylib 0x000000010da6826c vtkCommand::GetPassiveObserver() + 12 (vtkCommand.h:374)
1 libvtkCommon.5.10.dylib 0x000000011b4b5f52 vtkSubjectHelper::InvokeEvent(unsigned long, void, vtkObject) + 2082 (vtkObject.cxx:595)
2 libvtkCommon.5.10.dylib 0x000000011b4b6602 vtkObject::InvokeEvent(unsigned long, void) + 66 (vtkObject.cxx:770)
3 libvtkCommon.5.10.dylib 0x000000011b4b67e2 vtkObject::Modified() + 66 (vtkObject.cxx:837)
4 libMRMLCLI.dylib 0x000000010e419484 vtkMRMLNode::Modified() + 52 (vtkMRMLNode.h:348)
5 libMRMLCore.dylib 0x000000010e576dc1 vtkMRMLDisplayableNode::SetAndObserveNthDisplayNodeID(int, char const) + 1825 (vtkMRMLDisplayableNode.cxx:326)
6 libMRMLCore.dylib 0x000000010e578205 vtkMRMLDisplayableNode::RemoveNthDisplayNodeID(int) + 37 (vtkMRMLDisplayableNode.h:288)
7 libMRMLCore.dylib 0x000000010e57740a vtkMRMLDisplayableNode::UpdateReferences() + 186 (vtkMRMLDisplayableNode.cxx:187)
8 libMRMLCore.dylib 0x000000010e6bddb4 vtkMRMLScene::RemoveNode(vtkMRMLNode) + 2916 (vtkMRMLScene.cxx:1405)
9 libqMRMLWidgets.dylib 0x00000001059ab422 qMRMLVolumeInfoWidget::setLabelMap(bool) + 210 (qMRMLVolumeInfoWidget.cxx:443)
10 libqMRMLWidgets.dylib 0x00000001059c998e qMRMLVolumeInfoWidget::qt_static_metacall(QObject, QMetaObject::Call, int, void) + 414 (moc_qMRMLVolumeInfoWidget.cxx:84)
11 QtCore 0x000000011130922e QMetaObject::activate(QObject, QMetaObject const, int, void) + 1566
12 QtGui 0x0000000110b80411 QAbstractButton::toggled(bool) + 49
13 QtGui 0x00000001108a46ec QAbstractButton::setChecked(bool) + 156
14 QtGui 0x00000001108b7bd5 QCheckBox::nextCheckState() + 85
15 QtGui 0x00000001108a42c9 QAbstractButtonPrivate::click() + 89
16 QtGui 0x00000001108a4561 QAbstractButton::mouseReleaseEvent(QMouseEvent) + 113
17 QtGui 0x0000000110558651 QWidget::event(QEvent) + 2369
18 QtGui 0x00000001108a3358 QAbstractButton::event(QEvent) + 40
19 QtGui 0x00000001108b7c45 QCheckBox::event(QEvent) + 53
20 QtGui 0x000000011050093d QApplicationPrivate::notify_helper(QObject, QEvent) + 189
21 QtGui 0x00000001105072f0 QApplication::notify(QObject, QEvent) + 2384
22 QtCore 0x00000001112f117c QCoreApplication::notifyInternal(QObject, QEvent) + 124
23 QtGui 0x000000011050512d QApplicationPrivate::sendMouseEvent(QWidget, QMouseEvent, QWidget, QWidget, QWidget, QPointer<QWidget>&, bool) + 333
24 QtGui 0x00000001104b4985 qt_mac_handleMouseEvent(NSEvent, QEvent::Type, Qt::MouseButton, QWidget) + 741
25 com.apple.AppKit 0x00007fff9959340e -[NSWindow sendEvent:] + 6504
26 QtGui 0x00000001104a9a37 -[QCocoaWindow sendEvent:] + 87
27 com.apple.AppKit 0x00007fff9952ca55 -[NSApplication sendEvent:] + 5593
28 QtGui 0x00000001104aeb24 -[QNSApplication sendEvent:] + 84
29 com.apple.AppKit 0x00007fff994c30c6 -[NSApplication run] + 555
30 QtGui 0x00000001104b9900 QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 1824
31 QtCore 0x00000001112f0094 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 68
32 QtCore 0x00000001112f0444 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 324
33 QtCore 0x00000001112f2b2c QCoreApplication::exec() + 188
34 0x000000010537be6b (anonymous namespace)::SlicerAppMain(int, char) + 4283 (Main.cxx:365)
35 0x000000010537ada2 main + 34 (Main.cxx:397)
36 0x000000010537ad74 start + 52

I was not able to replicate this again - perhaps some other fix took care of the underlying issue.

To make sure we are doing the same thing, please use the attached self test script - put it in a directory and set it as an additional module path in the application settings. After restart you will find the module in Testing->TestCases->labelToggleBug2049 and you can run it with the Reload and Test button.

If you can get it to crash, please report here. If you want, you can edit the python script and reload and test to see if you can identify a sequence of operations that leads to a crash.

-Steve

If you can test that this still occurs (either manually or with the script) then I'll look into it some more. Otherwise I will close it and assume it has been fixed.

This is also checked in as a ctest (labelToggleBut2409) and as a runtime self test available from the Testing->TestCases menu.

I'm rebuilding Slicer and test it as soon as it's ready.

Seems to be fixed. Cannot reproduce anymore. Tested on Slicer-4.1.0-2012-09-03-win-amd64.exe.