Hard Crashes after 1.5.1 Update

Hallooo!

Hmm. So, I’ve just updated to 1.5.1 (13694) via “Check for Updates” and clicking the “Install and Relaunch”. Now, any .scap I attempt to open results in a hard crash. New documents seem to work alright, though they appear to have intermittent momentary freezes (could be unrelated, but worth mentioning). All .scap files authored in any prior release crash instantly. They crash so violently the fan spins up on my Mac Book Pro. :blush:

Here’s a partial crash report:

Process: Scapple [37446]
Path: /Applications/Scapple.app/Contents/MacOS/Scapple
Identifier: com.literatureandlatte.scapple
Version: 1.5.1 (13694)
Code Type: X86-64 (Native)
Parent Process: launchd [1]

Date/Time: 2025-09-13 09:54:25.6483 -0700
OS Version: macOS 13.4 (22F66)
Report Version: 12
Bridge OS Version: 7.5 (20P5058)

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 0x000000000000001e
Exception Codes: 0x0000000000000001, 0x000000000000001e

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

Anyone else experience this? Any chance there’s a workaround?

Cheers & Thanks :wink:

1 Like

Have you gone through the recent crash reports for Scapple on macOS yet, to see if there is anything matching your case?

1 Like

Amber, thank you. I did look through these, but your nudge led me to dig deeper. I went ahead and tried the 1.5.2 beta you shared in a previous thread. Sorted me right out. Woo! I’m back in the game. :slight_smile:

You rock. Thanks. :wink:

1 Like

Splendid, glad to hear we have nothing new to worry about. :slight_smile:

(Well, we do, but I think I’ve just about figured out the limits of it, and it is unique to macOS 26.)

1 Like

Thankfully, every time you finish stabilizing your beautiful app…every OS launches an update and sends you back in for more fixing. :laughing:

God speed! Y’all are doin great.

1 Like

You don’t even want to get me started on this update, in particular. :rofl:

1 Like