Program instantly crashing after uploading any sort of image files

[raidersofthelostgland]

Whenever trying to upload a new .mrxs file (microscopy image) to a new FastPathology project, the program instantly crashes without warning. FastPathology had been successfully using these files up until this point, so this is a sudden and new issue. I downloaded this program 2 weeks ago (mid-October). The issue is not isolated to my Macbook and also occurred when trying to download / install the software for the first time on a different Macbook.

System:
MacOS 14.1

Error Message - below is the error message that Mac generates when FastPathology crashes
Process: fastpathology [15664]
Path: /Applications/FastPathology.app/Contents/MacOS/bin/fastpathology
Identifier: fastpathology
Version: ???
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2024-10-31 16:01:43.2175 +0100
OS Version: macOS 14.1 (23B2073)
Report Version: 12
Anonymous UUID: 707BF885-583E-578D-2923-3E58B9612885

Sleep/Wake UUID: 18BB3F2D-4F5D-462D-8B6B-E3A61DD82197

Time Awake Since Boot: 38000 seconds
Time Since Wake: 812 seconds

System Integrity Protection: enabled

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000

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

VM Region Info: 0 is not in any region. Bytes before following region: 4369416192
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 104700000-104830000 [ 1216K] r-x/r-x SM=COW ...fastpathology

[andreped]

Hello @raidersofthelostgland :]

I am a bit busy for the next wo weeks, so I do not have time to assist you on this in much detail until then, unfortunately.

However, there are others that had issues using the mrxs format here. Perhaps read that thread to see if this may be what is causing your issues.

To assist you further, it would be nice to know exactly what went wrong. That is possible if you launch FastPathology from the terminal with enabled verbosity. Could you open a terminal and write the following:

/Applications/FastPathology.app/Contents/MacOS/bin/fastpathology --verbose

Then you can try opening the image you had issues with, and you should be able to see in more detail what went wrong.