Slicer crashes on startup due to SlicerVMTK extension

Support
1

Issue: On Slicer 5.12.2, Slicer crashes on startup after restarting Slicer following installation of SlicerVMTK. The startup log shows module loading failures in SlicerVMTK due to unresolved dylib dependencies, including libdcmjp2kcs.20.dylib looking for libopenjp2.7.dylib and libssl.1.1.dylib referencing a bad install name (/D/S/A/OpenSSL/libcrypto.1.1.dylib). The crash happens during module instantiation while Slicer is loading extensions.

Specs: macOS Tahoe on 2026 MacBook Pro with M5 Pro chip

Other: I also tried installing SlicerVMTK on Slicer 5.10.0 and did not encounter any issues.

2

This macos specific, and related to this bug being tracked: COMP: Update DCMTKcs to fix OpenJPEG over-linking on macOS by lassoan · Pull Request #9263 · Slicer/Slicer · GitHub

Until that’s fixed and a new patch release is cut, your easiest option is to use windows or linux version.

3

Thanks @muratmaga for the info. I see that PR is merged and I don’t see any linked issues. Is there other work to be done to fix this bug?

4

I do not know if there are any other work that needs to be done, but cutting a new release from scratch (like this) in itself takes a few days. Meanwhile I think the previews are fine (though I didn’t try it personnally).

5

The PR fixing the original issue is merged, but for some macOS-specific reason that I don’t yet understand there is a further problem that only applies to signed+notarized releases. The preview releases are unsigned, making them okay

6

Sorry for the inconvenience. Until Slicer-5.12 is fixed, you can use a Slicer Preview Release (Slicer-5.13) on macOS if you need to use any extensions that contain C++ modules.

7

I submitted an issue that we can mention at all related error reports and people can follow to get updates: