Sublime Forum

Dev Build 3121

#1

Dev Build 3121 is out now, details are at https://www.sublimetext.com/3dev

5 Likes
Module error when running a plugin
#2

3121 seems to hog the CPUs.

When I autoupdated, upon restart I see 3 process created, where 2 of them end up pegging all of my CPUs. I downgraded to 3120 to recover for now.

I am on OSX El Capitan 10.11.6.

0 Likes
#3

It’s probably re-indexing your project, which needs to be done after any change to the syntax definitions - check for a percentage indicator in the status bar

0 Likes
#4

Sublime has now crashed on me twice in the last half hour. Checking Console all I get is:
9/13/16 4:30:55.577 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.oneshot.0x10000019.Sublime Text[13901]) Service exited with abnormal code: 1

I’ll see if I can get more info but it miiiiight be related to keyboard events?

0 Likes
#5

And just at that time I was going trough the updates in the issue list of the past month, so I closed a few issues while I was at it: https://github.com/SublimeTextIssues/Core/issues?utf8=✓&q=is%3Aissue%20milestone%3A"Build%203121"%20.

@wbond, feel free to confirm on the “maybe fixed” issues or close more, as always.

1 Like
#6

I’m also getting the same error frequently - same console message. For me it was happening consistently a few seconds after opening a sass ‘.scss’ file. Disabling the “ColorHelper” package seems to have stopped it happening for now.

0 Likes
#7

Spoke too soon. Crashing still occurring, although intermittent. Haven’t pinpointed the cause yet.

0 Likes
#8

Tabs containing .slim and .scss files opened empty, as did new tabs with unsaved contents, which appear to be lost.

With the Ruby Slim plugin indexing gets to 93% and stops, pegging 5 cores, and eventually dropping to 4 processes and causing the editor to stop responding. SCSS plugin also errors, resulting in those files opening empty. Seems OK with both plugins removed.

0 Likes
#9

Yes, 4 crashes happened this morning after upgrade.

0 Likes
#10

Not crashed even once, but ColorHelper did start to malfunction a little bit.

Probably just something incompatible in Slim and SCSS, and I happen to use neither of them.

0 Likes
#11

Also seeing crashes… For a while I was able to get one consistently just by scrolling up and down in a particular css file, but that’s no longer happening…

OSX El Capitan 10.11.6.

0 Likes
#12

OSX 10.12 GM, just shows the release notes and dies.

0 Likes
#13

After update, some users report me some relative import errors… Not analyzed yet, but probably not plugin specific

0 Likes
#14

ST was turn off when I scroll to end of the file (each time I try it)

0 Likes
#15

Sublime crawlers were using about 50% of my CPU since the update to 3121 for a good half hour. But I didn’t see any percentage in the status bar.

0 Likes
#16

Same here, crash whenever I save a file :frowning:

0 Likes
#17

I made another thread before spotting this one, but I’m also seeing issues. As of updating to 3121 the Ruby Test runner package crashes Sublime anytime I use it.

0 Likes
#18

ST has crashed ~10 times for me this morning. Now getting quite frustrated. Is there a way to download the old dev build?

FYI, it has crashed when doing a variety of different things so I can’t pin down the reason.

0 Likes
#19

For those that might be interested, older builds can be downloaded by amending the download url:

Build 3121 (current): https://download.sublimetext.com/Sublime%20Text%20Build%203121.dmg
Build 3120: https://download.sublimetext.com/Sublime%20Text%20Build%203120.dmg
Build 3119: https://download.sublimetext.com/Sublime%20Text%20Build%203119.dmg

0 Likes
#20

For those experiencing crashes, can you provide some info:

  1. What platform you are on
  2. Do you see crashes in a clean state? (http://www.sublimetext.com/docs/3/revert.html, save your data directory to restore afterwards)
2 Likes