Help for package testing on macOS Monterrey or BigSur system

Development
1

Context

To perform some testing to check if issue Slicer#6347 reported by @che85 is specific to recent macOS system or if it is related to specific network & proxy settings.

Help needed

Two ways you could help:

  1. Reach out privately to @jcfr to schedule a hangout

  2. Perform these steps and report back:

    • Download this package
    • Open and “move” the application into your download folder.
      • :warning: Do not directly run from the mounted application
    • Right click on Slicer application, select Open
      • :warning: since this package is not yet signed, you will likely have to accept the warning and try twice.
    • Click on the extension manager icon image
    • Attempt to install any extension
    • Question: Is an error like the following is reported after clicking on the “Install” button ? image
2

How recent of a preview release to test this?

3

Since the issue indicates

just tested on older Slicer preview versions and it’s happening for all of them.

feedback related to a recent installation of a preview build would be helpful too if that it is easier for you to check.

4

DOH - should have read issue, sorry. Checking.

5

I did not get the error described above - the extensions installed correctly (SlicerMorph, which includes a few extensions, etc).

I did get a crash on exit, however - stack trace below. Re-opening Slicer, trying an extension, and then exiting Slicer dit not repeat the crash.

This is on macOS Monterey 12.1, MacBook Pro 16" (2019).

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               Slicer [4415]
Path:                  /Users/USER/Downloads/Slicer.app/Contents/MacOS/Slicer
Identifier:            org.slicer.slicer
Version:               5.0.1 (5.0.1)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2022-05-02 18:30:59.0736 -0400
OS Version:            macOS 12.1 (21C52)
Report Version:        12
Bridge OS Version:     6.1 (19P647)
Anonymous UUID:        35B3F1AE-3AB0-EA88-9149-17BDBEC361AB

Sleep/Wake UUID:       733D78D9-C625-4583-8C2D-569FE60E808B

Time Awake Since Boot: 62000 seconds
Time Since Wake:       7698 seconds

System Integrity Protection: enabled

Crashed Thread:        0  CrBrowserMain  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       UNKNOWN_0xD at 0x0000000000000000
Exception Codes:       0x000000000000000d, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [4415]

VM Region Info: 0 is not in any region.  Bytes before following region: 4502261760
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      10c5b1000-10c5f3000    [  264K] r-x/rwx SM=COW  .../MacOS/Slicer

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0   QtWidgets                     	       0x10dd46675 QWidgetPrivate::setParent_sys(QWidget*, QFlags<Qt::WindowType>) + 37
1   QtWidgets                     	       0x10dd3099d QWidget::setParent(QWidget*, QFlags<Qt::WindowType>) + 637
2   libqSlicerBaseQTGUI.dylib     	       0x10cd64063 qSlicerApplicationPrivate::~qSlicerApplicationPrivate() + 131
3   libqSlicerBaseQTGUI.dylib     	       0x10cd6413e qSlicerApplicationPrivate::~qSlicerApplicationPrivate() + 14
4   libqSlicerBaseQTCore.dylib    	       0x10d6513e6 qSlicerCoreApplication::~qSlicerCoreApplication() + 38
5   Slicer                        	       0x10c5eeb0f main + 527
6   dyld                          	       0x10e5ef4fe start + 462
6

Thanks for the feedback that is very helpful. Thanks for taking the time :pray:

The crash is unfortunate, I would be curious is this is systematic after installing extension.

7

I also got the crash on exit after running the extension manager. Install worked for Segmentation Extra Effects, so probably not extension-specific. Oddly it’s a slightly different stack trace.

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               Slicer [3899]
Path:                  /Users/USER/Downloads/Slicer.app/Contents/MacOS/Slicer
Identifier:            org.slicer.slicer
Version:               5.0.1 (5.0.1)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2022-05-02 19:33:22.3666 -0400
OS Version:            macOS 12.3.1 (21E258)
Report Version:        12
Bridge OS Version:     6.4 (19P4243)
Anonymous UUID:        3797FBED-83D2-B47D-D4EA-26F22AA011DE


Time Awake Since Boot: 1300 seconds

System Integrity Protection: enabled

Crashed Thread:        0  CrBrowserMain  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       UNKNOWN_0xD at 0x0000000000000000
Exception Codes:       0x000000000000000d, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [3899]

VM Region Info: 0 is not in any region.  Bytes before following region: 4525027328
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      10db67000-10dba9000    [  264K] r-x/rwx SM=COW  .../MacOS/Slicer

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0   libqSlicerBaseQTGUI.dylib     	       0x10e31a072 qSlicerApplicationPrivate::~qSlicerApplicationPrivate() + 146
1   libqSlicerBaseQTGUI.dylib     	       0x10e31a13e qSlicerApplicationPrivate::~qSlicerApplicationPrivate() + 14
2   libqSlicerBaseQTCore.dylib    	       0x10ec073e6 qSlicerCoreApplication::~qSlicerCoreApplication() + 38
3   Slicer                        	       0x10dba4b0f main + 527
4   dyld                          	       0x112fbf51e start + 462

<cruft removed>
8

Thanks @hherhold @RafaelPalomar @pieper @lassoan @mau_igna_06 for the help, during today’s hangout we identified the issue and will be submitting a fix.

we will then release v5.0.3

1 Like
9

To close the loop, here is the associated fix: BUG: Fix on exit Segfault ensuring ExtensionsManagerDialog is deleted once by jcfr · Pull Request #6348 · Slicer/Slicer · GitHub

10

It turns out, that I had an outdated OpenSSL version installed which is the reason why I couldn’t install any extensions.