Sublime Forum

Problems after updating to macOS Sequoia

#1

Following issue also posted to github - https://github.com/sublimehq/sublime_text/issues/6537

After updating laptop to MacOS Sequoia 15.1.1 (24B91) Sublime Text (build number 4180) is now supper laggy with response to keyboard input, to the point of being unusable. When I type the characters show up in the document 2-3 seconds after they are typed. No characters show up on the screen and then 10 of them are dumped into the document all at once.

Other text editors are not having a problem, e.g. TextEdit, Visual Studio Code, so this is not a keyboard problem. This is a Sublime Text + macOS update problem.

Any advice on how to fix this is appreciated. Maybe some OS setting can be disabled? This smells like a macOS bug that is impacting Sublime Text, not the other way around. Could the Sublime maintainers please reach out to Apple to see what has changed that broke the input signal flow for Sublime Text?

Side note: Laptop is a Apple M2 Pro

0 Likes
#3

What ever that bug was, it was fixed by Build 4189 released 20 Dec 2024

0 Likes
#4

No. I was wrong. This is not fixed with the Sublime latest release.

I discovered the key delay issue happens whenever my Macbook is plugged into my external ASUS display. I’m absolutely sure this is what provokes the problem.

If I unplug the external display Sublime Text key entry works normally. If I plug the display in, then the key entry gets very laggy, where nothing shows up and then whole words I typed get spilled into the document. It doesn’t matter what display the Sublime is rendered on, this issue is specifically tied to the display being plugged in.

0 Likes
#5

I finally found a fix for the issue.

I’m leaving the git issue open because it seems like the maintainers of Sublime Test should make a correction for Mac external display users on macOS Sequoia or put a warning somewhere with instruction on how to deal with this issue.

Adding the following in settings…/settings made the key entry delay bug go away…

{
  "gpu_window_buffer": false,
  "hardware_acceleration": "none"
}

The default is: "hardware_acceleration": "none"
So the more effective line is: "gpu_window_buffer": false

0 Likes
#6

Note "gpu_window_buffer" does not exist anymore and has been replaced by "hardware_acceleration". The default for macOS is "hardware_acceleration": "opengl".

This sounds like a OpenGL driver bug - Apple commonly introduces driver bugs in major updates.

0 Likes