Sublime Forum

Sublime Text 4180 and 4200 crash on launch macOS 26.3.1

#1

Sublime Text 4180 and 4200 crash on launch on my m1 max macbook pro running macOS 26.3.1.

I tried renaming the “~/Library/Application Support/Sublime Text” folder to something else so it couldn’t be found, and also deleting the “~/Library/Preferences/com.sublimetext.4.plist” but the program still crashes on launch.

Any ideas?

0 Likes
#2

Does it happen in safe mode? You can get logs by running Sublime\ Text.app/Contents/MacOS/sublime_text --multiinstance --debug from a terminal.

0 Likes
#3

Nope, it doesn’t run in safe mode. Here is the output with username / machinename replacing my details:

(base) username@machinename ~ % /Applications/Sublime\ Text.app/Contents/MacOS/sublime_text --multiinstance --debug
:0                                                                startup, version: 4200 osx arm64 channel: stable
:0                                                                executable: /Applications/Sublime Text.app/Contents/MacOS/sublime_text
:0                                                                application: /Applications/Sublime Text.app
:0                                                                working dir: /Users/username
:0                                                                packages path: /Users/username/Library/Application Support/Sublime Text/Packages
:0                                                                state path: /Users/username/Library/Application Support/Sublime Text/Local
Unable to init shm: Failed to create semaphore
(base) username@machinename ~ %
0 Likes
#4

That looks to me like either there’s too many semaphores or too much shared memory on your system. Rebooting would likely fix the issue. Did this suddenly start happening or have you been using Sublime Text for a while?

0 Likes
#5

Rebooting did not help, and this is not to do with a ram shortage etc. This happened when I updated to macos 26.3.1, all was good before. I just updated to macos 26.4.0 and it looks like the issue has been resolved, sublime text is now loading again just fine. I am guessing this was a bug in macos 26.3.x to do with how semaphores were handled against various sdks.

1 Like