Sublime Forum

ST3 Freezing up on anyone else?

#21

Same problem here. Have gotten rid of the plugins noted. Opening a 600 line compiled CSS file is almost impossible and takes a good 20-30 seconds. The same with a 74 line Sass variables file. PHP and js files are normal. I am using the 64 bit version. If the Sass file is open when I open ST3, it will take 20 seconds before its usuable.

Can I uninstall and install the 32 bit without losing all my plugins and settings?

0 Likes
#22

On Mac.
cd ~/Library/Application\ Support/Sublime\ Text\ 3/Local
ls -ln
rm Auto Save Session.sublime_session

This will create a new session and eliminate whatever was causing the app crash. I would also disable and enable plugins one by one to check if thatā€™s causing any crashes.

1 Like
#23

Tried with a fresh install (moved the Sublime Text 3 folder elsewhere) and the problem is still present.
Downgraded to an older version and in two weeks I had no freeze.
my problem is not plugin related.

Thanks,
Frank

0 Likes
#24

I followed what artem328 did and moved my ~/.config/sublime-text3 to ~/.config/sublime-text31 then started sublime againā€¦Still frozenā€¦So I deleted the new ~/.config/sublime-text3 directory and copied ~/.config/sublime-text31 back to ~/.config/sublime-text3 AND IT WORKED

0 Likes
#25

Same exact thing happens to me.

0 Likes
#26

It may be a problem with circular symbolic links. I just started having the freezing problem so I added my build folder to the "folder_exclude_patterns": in the Sublime settings and it seems to be ok now. I think it was causing circular indexing that would never end. Somehow, over-night, my build structure must have added a symlink that completed the infinite symlink loop when I built some package or something from source.

0 Likes
#27

Confirmed! If I open up that project and comment out the excluded folder, then resave my settings, I get instant freezing again in the very moment I click the save button. The indexer must be stuck infinitely indexing.

0 Likes
#28

I couldnā€™t even open Sublime Text after this. I had to force kill it by running xkill from a terminal then clicking the window to close, then I had to manually go to ~/.config/sublime-text-3/Packages/User/Preferences.sublime-settings and open the file in an alternate text editor to fix it. I then had to restart my computer and open up Sublime again. Now that I have excluded the culprit folder again in this settings file Sublime Text 3 opens and works just fine!

Perhaps there is some way for the developer to identify circular symlinks and not follow them indefinitely?

PS hereā€™s my Sublime settings file now:

{
	"color_scheme": "Packages/Color Scheme - Default/Monokai.tmTheme",
	"folder_exclude_patterns":
	[
		".svn",
		".git",
		".hg",
		"CVS",
		"build_folder_with_circular_symbolic_links*" //THIS IS IMPORTANT! OTHERWISE THERE ARE CIRCULAR SYMLINKS OR SOMETHING AND SUBLIME WILL CONTINUALLY CRASH!
	],
	"ignored_packages":
	[
		"Vintage"
	],
	"rulers":
	[
		120
	],
	"tab_size": 4,
	"theme": "Default.sublime-theme",
	"translate_tabs_to_spaces": true,
	"word_wrap": "auto",
	"wrap_width": 0
}
0 Likes
#29

We currently do this by checking the inode information of a folder, and we donā€™t catalog the contents if weā€™ve seen it before. The reflection of this in the UI using the Default theme is a folder with a chain link on it.

The question is, what is going on with your machine that a symlink is resulting in different inode numbers so that we are infinitely cataloging a recursive structure. That is, assuming what is going on.

0 Likes
#30

What is you Operating System and Sublime Text version? You can run these commands:

uname -or
lsb_release -irc
0 Likes
#31

uname -or
4.4.0-103-generic GNU/Linux

lsb_release -irc
Distributor ID: Ubuntu
Release: 14.04
Codename: trusty

0 Likes
#32

Your views helps me a lot for resolve my issue. thank you

0 Likes