Sublime Forum

**wbond** · September 22, 2016, 7:50pm

What Jade syntax are you using? Can you provide an example of a .jade file that causes ST to hang?

Have you tried installing a newer version of the JavaScript syntax, as discussed at [Solved] High CPU Usage in Beta 3124?

**bbassett** · September 22, 2016, 7:55pm

Here is an example of a .jade file

:doc
  @name Toolbar
  @props {Boolean} [left]
  @props {Boolean} [center]
  @props {Boolean} [right]

import './index.ess'

var classFn = this.composeClasses('Toolbar')

.Toolbar(className=classFn())
  div(className=classFn('&-inner'))
    if props.left
      div(className=classFn('&-left'))
        yield left

    if props.center
      div(className=classFn('&-center'))
        yield center

    if props.right
      div(className=classFn('&-right'))
        yield right

:module
  export var mixins = [require('ui-kit/mixins/compose-classes')]

I haven’t tried updating my js syntax, i’ll try that now. Is there a way to reset the state on ST? i can’t open it currently because of the feature of re-opening files where i left off, so it re-opens a file that it is hanging on, and all i can do is force quit.

(FYI, i’m on OSX El Capitan)

**wbond** · September 22, 2016, 7:56pm

You could wipe your Local/Session.sublime-session file, but you probably don’t want to do that. Installing the JavaScript.sublime-syntax override is likely to fix what you are running into.

**bbassett** · September 22, 2016, 7:59pm

Why wouldn’t i want to wipe the Local/Session.sublime-session file? I’m not worried about losing any changes, if that is the concern there.

**wbond** · September 22, 2016, 8:02pm

It just kills all of your history (recent projects, searches, and more). Any adjustments you’ve made to the size of UI panels, or options, like the Find panel.

**bbassett** · September 22, 2016, 8:11pm

Well, i killed it, it was a choice between ST not working at all, re-installing, or just losing that, which i would have anyway for the other two options. Adding the Javascript.sublime-syntax override did solve my problem. Has the underlying problem been diagnosed? I have about 30 colleagues who will all have this issue when they update. I warned them all this morning to not update because of this

**wbond** · September 22, 2016, 8:28pm

The underlying issue is that the Jade syntax uses regex constructs that aren’t supported by our newer regex engine. It ends up including the JavaScript syntax that ships with Sublime Text. That syntax uses a regex that works fine on a non-backtracking engine (like our newer engine), but once combined with the regexes from Jade it causes catastrophic backtracking in the Oniguruma engine.

Unfortunately it seems that none of the users of the dev builds utilize the Jade syntax, nor the MarkdownEditing syntax with fenced js code blocks.

**kingkeith** · September 22, 2016, 8:37pm

I’m a dev build user and I refuse to use any syntax that won’t use the sregex engine, so that’s why I never discovered it

it shows how important it is to get an even more diverse group of people on the dev builds though… consider using them, people!

**bbassett** · September 22, 2016, 8:39pm

Well that’s unfortunate. I’ll let my team know about the override. Anyway, thanks for all the help! I’ll check into using the dev builds, maybe i can at least cover the jade syntax issues.

lol and maybe some day i’ll have the luxury of choosing my syntax, but today is not that day. And, honestly i love the dev perks of using jade, it’s unfortunate that it’s conflicting so bad with ST

**kingkeith** · September 22, 2016, 8:40pm

I guess I’m special in that I manage to find the time to hack together my own syntax that is suitable enough for my needs I don’t tend to regularly work on many different file types though, which makes it easier

**stevage** · September 23, 2016, 1:40am

Hi WBond,
Thanks for the update…but I guess I’m kind of wondering if there is a bigger fix possible? I’ve been reporting the miserable experiences that indexing and broken plugins create for a long time now. For anyone developing NodeJS (and probably other dependency-heavy platforms as well), huge directory trees are the norm - not an edge case.

Could Sublime:

be smarter about whether to index dependencies by default?
count the number of files to be indexed, and warn the user when a massive indexing job is about to start?
drop the priority of long-running indexing tasks so they don’t take over your whole computer?
give the user better feedback about what’s going on?
detect plugins that are known to be problematic and warn the user, offering to disable them?

This is probably the 4th or 5th time I’ve had a situation where some change (plugin, new Sublime build, etc) causes my whole editing experience to grind to a halt, and the solution always involves hackily editing config files, looking under the hood etc. Surely my experience is not rare.

**wbond** · September 23, 2016, 11:49am

Could everyone install dev build 3125 and see how it helps?

We’ve included the JavaScript change, but also made some tweaks to the default number of index_workers. Jon created a new Help > Index Status… window to show all of the indexing activity.

We’ve got some more tweaks planned for the future, but hopefully these changes should help users experiencing acute behavior.

**wbond** · September 23, 2016, 12:02pm

Fundamentally there really aren’t issues with large folder trees. I dogfood ST on a daily basis with projects of around 100k files and regularly work on the syntax definitions, where saving a syntax definition triggers reindexing.

We made a tweak in 3125 to the default number of workers that should address users who don’t care for fans spinning up on their laptops.

Sublime Text already sets indexers as low priority. While it is true that the indexers will use spare CPU, it shouldn’t really “take over” unless the OS has trouble scheduling. Our tweak to the default number of indexers should help reduce this symptom.

The Console shows errors in indexing, to allow the user to find issues with syntaxes. The progress of indexing is displayed in the status bar, and there is a new Index Status window in build 3125 allowing users to see exactly what is going on.

We’ve got some ideas about further ways we can make the indexing process even more robust.

One of the best ways to help ensure that betas don’t run into situations like we are discussing here is to help test the dev builds and help test the third-party packages you use with the dev builds.

**bbassett** · September 23, 2016, 7:11pm

I switched to build 3125 and removed my Javascript.sublime-syntax and the indexing seems to have worked properly (the output was error free). Thanks for the fix! i’ll try and keep up with dev builds in the future.

**brianthecoder** · September 23, 2016, 8:42pm

I can’t even paste with out having it hang. Not sure how such a basic functionality could do that. I’ve exited and restarted about 6 times in the past 10 minutes. Also it is just 3 lines of code. I’m probably just going to switch to Atom this weekend

**wbond** · September 23, 2016, 8:42pm

Is this build 3125 you are talking about? If so, what syntax are you using when you try to paste?

**brianthecoder** · September 23, 2016, 8:43pm

This is 3124. I am trying to paste a simple html snippet. In to a 95 line file

**wbond** · September 23, 2016, 8:47pm

Oh, you should try dev build 3125 and confirm that it works.

The issue is that a third-party package you have installed (MarkdownEditing, Jade, or possibly some other) uses regexes that combined with regexes in the default JavaScript syntax cause catastrophic backtracking on the Oniguruma regex engine when combined with certain code.

We shipped a dev build with a fix for it last night and are planning to ship a new beta shortly.

**brianthecoder** · September 23, 2016, 9:10pm

I may when I am less mad at sublime. With the latest updates I’ve probably lost an hour or so. Not counting the times I lost work because I tried to paste like a fool. I mean the background updates of packages usually makes it hang for about 10 minutes with no indication of what is going on

**wbond** · September 23, 2016, 9:34pm

Beta 3126 has been released.

Thanks everyone for helping to identify the issue!