Sublime Forum

Build 3208 performance regression

#2

Same here… terrible lag peformance with 3208

1 Like
#3

Unfortunately macOS 10.14.4 introduced a number of issues to the NSOpenGLView class, causing it to be extremely crash-prone and easily cause memory leaks. Because of this we’ve had to disable our usage of NSOpenGLView since most users will just assume the crashes are our fault.

The downside here is that NSOpenGLView is how we get nice smooth scrolling on 5K displays.

You options are:

  • Downgrade to macOS 10.14.3
  • Downgrage to Sublime Text 3207
  • Install macOS 10.14.5 Beta 2 (I personally am not going to recommend this since it may interrupt your workflow in other ways)
  • Deal with the lagginess until 10.14.5 is released
0 Likes
#4

Thanks! Downgrading to 3207 fixed it for me. I’ll be stuck on this version for a while, until macOS 10.14.5 gets released at least.

1 Like
#5

Is Apple interested in fixing OpenGL regressions? Last I remember, they were going to drop the API altogether.

0 Likes
#6

I do believe they have deprecated OpenGL in favor of Metal, but breaking it on a bug fix release isn’t exactly their M.O. in terms of deprecation.

I would expect with a major release they would finally remove it. Until then, I think it is reasonable for their APIs to not be totally borked with crashes and massive memory leaks.

0 Likes
#7

Agreed, and I definitely don’t fault you guys for it. I’m just mildly sceptical about Apple’s motivation to fix something that’s already on the chopping block.

0 Likes
#8

Wowowowow. I wondered why my ST was so slow today, I thought it was a plugin I’ve got but I’ve tried 3207 and 3208, it’s clearly the update which breaks the performance of ST (due to macOS as you said yeah).

I’ll stay on 3207 too so. Thank you for the detail. :slight_smile:

0 Likes
#9

@wbond Is there a way I can just… turn off the workaround? I didn’t experience any crashes previous to its introduction, and the lagginess is… very very oppressive.

Worth noting that I’m not on a 5k display. This is just a stock MacBook Pro.

0 Likes
#10

To turn off the workaround, roll back to 3207 for now.

0 Likes
#11

Yeah that’s what I did. I was hoping there would be a way I could do it without suspending updates.

0 Likes
#12

Yeah I would like say I also had no crash trouble at all with 3207.

1 Like
#13

Worth adding that prior to 3208 I also had no issues with OpenGL that I could tell, working in ST3 full time, always on.

0 Likes
#14

I did a new homebrew formula for 3207 if needed: https://gist.github.com/kud/651f874a1b9e3878a5fb11cb15566cf1

1 Like
#15

And I started to think I was crazy or all of a sudden a plugin started to block my editor.

Are there any plans to support Metal on the Mac?

0 Likes
#16

How do I use this homebrew formula for 3207?
Does it persist my settings from my main sublime installation?

0 Likes
#17

@slifin Click on “raw” button, download it and do

$ brew cask uninstall sublime-text-dev
$ brew cask install /path/of/the/sublime-text-dev.rb

It won’t remove your settings as they’re in /Users/username/Library/Application Support/Sublime Text 3. You can back 'em up if you’re a bit afraid to lose them. :slight_smile:

2 Likes
#18

macOS 10.14.5 is released and has reportedly fixed Alacritty’s OGL problem. Anyone want to give 3208 another shot? :wink:

0 Likes
Crash or Memory Leak on macOS Mojave 10.14.4?
#19

Both 3207 and 3208 should work fine with 10.14.5, assuming that Apple fixed the OpenGL bugs.

The mitigations were targeted at 10.14.4 specifically, so they should not kick in with 10.14.5.

3 Likes
#20

Just to confirm, after updating MacOS to 10.14.5 and switching back to build 3208 of ST3, the lag is no longer there. :+1: However, as per @wbond this is probably because mitigations are ignoring that MacOS version, and not necessarily because all OpenGL issues were fixed. One can hope. :crossed_fingers:

0 Likes
#21

It seems indeed better on 10.14.5. :slight_smile:

0 Likes