Sublime Forum

Sublime 3124 eat up my CPUs

#1

I upgrade to Sublime 3124 today, and it’s SUPER HIGH usage with ALL CPUs.

2 Likes

#2

The same for me on Windows. I followed suggestions to remove the “Index” directory (C:/users/username/AppData/Local/Sublime Text 3/Index), which did not work.

Is there a way to downgrade? -> I found a way to download 3114 which works like a charm!

1 Like

#3

Sublime Text is using background processes to index all of the source code in your project. This powers the Goto Definition functionality and Definitions popup.

In the status bar you will see a percentage that should be increasing. This shows the progress of the index workers in crawling all of the source code in your project. If this seems to be taking more than a minute or two for the first time you open a folder, it is likely that you either have a very large project, or possibly have an inefficient syntax definition installed for one of the main languages in your project. You can also check the Console to see if the index workers are running into errors.

Finally, you may find that tweaking the number of background index workers is to your liking. By default, one low-priority worker process is created per CPU core. On desktops this results in fast indexing. On some laptops this may cause the fan to kick on. You can tweak the index_workers setting in Preferences > Settings to 2 or 1 to see if it is a better fit for your setup.

2 Likes

Build 3124 Show Definition
[solved] 3124 is killing my cpu fan
#4

ST is indeed indexing with my Build 3124. It seems to be stuck on 7%. There’s one large section of my project which is the node_modules section of my Twitter Bootstrap sass installation ~ 147 MB with 20,000+ files. Anyway I can get it to ignore that?

Whilst it’s indexing it’s taking up 50% CPU and making other applications like Firefox sluggish.

0 Likes

#5

Ah - this looks promising: [solved] 3124 is killing my cpu fan

"index_exclude_patterns": ["*.log", "node_modules/*", "bower_components/*"]

0 Likes

#6

Have tried the index_exclude_patterns setting, but it still appears to be trying to index node_modules.

I’m getting the following in the console:

worker 9092 appears stuck while processing file /C/inetpub/wwwroot/xxx/app/webroot/bootstrap-3.3.6/node_modules/acorn-globals/README.md, killing process
worker 5388 appears stuck while processing file /C/inetpub/wwwroot/xxx/app/webroot/bootstrap-3.3.6/node_modules/argparse/node_modules/underscore.string/README.markdown, killing process
worker 9092 appears stuck while processing file /C/inetpub/wwwroot/xxx/app/webroot/bootstrap-3.3.6/node_modules/acorn-globals/README.md, killing process

Edit: Don’t know why it was stuck on those two files. But it looped over those two files trying to read them indefinitely.

so I added "*.md", "*.markdown" to the index_exclude_patterns. Ugly solution but has got me beyond 7%.

0 Likes

#7

If you open those files to you get any errors related to syntaxes?

1 Like

#8

yep… open up the README.markdown freezes up ST completely

Edit: and my indexing was at 95%… :disappointed:

Edit2: actually on opening ST again, indexing has stopped, i.e. it appears ok.

All is good, just as long as I don’t try opening the evil markdown file…

0 Likes

#9

Edit3: this is what I get opening the README.md file. Obviously a problem with the MarkdownEditing package. I’ll go and raise a bug there.

Someone beat me to it: https://github.com/SublimeText-Markdown/MarkdownEditing/issues/390

0 Likes

#10

How to see indexing progress? When I try to open a file with about 1k lines in a large project sublime just freezes. Pressing CMD+P and typing at least 1 character does the same. OSX El Capitan

0 Likes

#11

For those who still experiences the same problem, downgrading to 3114 helps https://download.sublimetext.com/Sublime%20Text%20Build%203114.dmg

0 Likes

#12

There’s a % symbol in the status bar at the bottom.

0 Likes

#13

Most likely there is a package installed that is causing issues. What kind of file are you trying to open? I would look for a package related to that file type.

0 Likes

#14

Ruby file, 27k characters, nothing suspicious.

Rubocop is disabled.

0 Likes

#15

Please, how do I revert??? ST3 keeps crashing and I’m having all sorts of slow performance and package issues

0 Likes

#16

Hearing this a lot lately. I think it would be worth having Sublime ignore node_modules by default as they can contain hundreds of thousands of files per project

2 Likes

#17

Just go to the download page https://www.sublimetext.com/3, copy the download link, paste it to your browsers address bar and change the build number (I took build number 3114), voila! Run the install program, everything will be there as if nothing happened.

0 Likes

#18

I’ve posted a sticky topic on this issue at [Solved] High CPU Usage in Beta 3124.

Reverting should (ideally) be a last resort. It doesn’t address the problem, and just means you’ll be stuck on an old version of the software without helping identify if there is a problem, or what the problem is.

3 Likes

#20

Dev Build 3125 came out with a workaround for this last night.

Apparently none of the users of the dev builds were using the third-party package causing the issue. The issue does not exist on a vanilla install.

1 Like

#21

Beta 3126 has been released

2 Likes