Sublime Forum

Sublime indexing forever in Mac , never stop

#1

sublime build 3154, mac os version 10.13.1 ,

PID    COMMAND      %CPU  TIME     #TH   #WQ  #PORTS MEM    PURG   CMPRS  PGRP  PPID  STATE    BOOSTS          %CPU_ME %CPU_OTHRS UID  FAULTS    COW     MSGSENT    MSGRECV    SYSBSD    SYSMACH
74506  Sublime Text 0.0   00:00.09 5/1   2    38+    6532K+ 0B     0B     69592 69592 running  *0[1+]          0.00000 0.00000    501  4612+     195+    523+       115+       10626+    5961+
74505  Sublime Text 99.6  00:01.25 6/1   2    39     30M+   0B     0B     69592 69592 running  *0[1]           0.00000 0.00000    501  10726+    195     529        124        11334+    5911+
0 Likes

#2

what packages do you have installed? what’s the output from Help -> Indexing Status?

0 Likes

#3
{
	"bootstrapped": true,
	"in_process_packages":
	[
	],
	"installed_packages":
	[
		"A File Icon",
		"Babel",
		"DA UI",
		"DocBlockr",
		"Dockerfile Syntax Highlighting",
		"Emmet",
		"File History",
		"GitGutter",
		"HTML-CSS-JS Prettify",
		"Markdown Preview",
		"MarkdownEditing",
		"Oceanic Next Color Scheme",
		"Origami",
		"Package Control",
		"Path Tools",
		"PHP Companion",
		"PHP Completions Kit",
		"PHP-Twig",
		"Phpcs",
		"phpfmt",
		"Pretty JSON",
		"Pretty YAML",
		"SideBarEnhancements",
		"SqlBeautifier"
	]
}

indexing [job 1]: spawning 1 workers to process 1 / 1 files
indexing [job 2]: spawning 1 workers to process 332 / 332 files
indexing [job 1]: indexed 1 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 332 / 332 files
indexing [job 2]: indexed 4 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
indexing [job 2]: spawning 2 workers to process 328 / 328 files
indexing [job 2]: indexed 0 files
0 Likes

#4

Having a similar issue:

indexing [job 1313]: indexed 3 files
indexing [job 1314]: spawning 2 workers to process 4096 / 45936 files
indexing [job 1314]: indexed 3 files
indexing [job 1315]: spawning 2 workers to process 4096 / 45936 files

Is there a way to log more verbosely what is being indexed?
I think my index_exclude_patterns aren’t working. Cant find proper documentation on where to set them on a per project basis and how these file and folder patterns are interpreted.

0 Likes

#5

I don’t think index_exclude_patterns can be set on a project basis:

also slightly related:

you can enter sublime.log_indexing(True) Enter in the ST Console (View menu -> Show Console), but it’s possible that it doesn’t have any affect atm:

0 Likes

#6

Same issues here:

indexing [job 241]: indexed 125 files
indexing [job 242]: spawning 1 workers to process 1737 / 1737 files
indexing [job 242]: indexed 125 files
indexing [job 243]: spawning 1 workers to process 1737 / 1737 files
indexing [job 243]: indexed 121 files
indexing [job 244]: spawning 1 workers to process 1737 / 1737 files
indexing [job 244]: indexed 109 files
indexing [job 245]: spawning 1 workers to process 1737 / 1737 files
indexing [job 245]: indexed 79 files
indexing [job 246]: spawning 1 workers to process 1737 / 1737 files
indexing [job 246]: indexed 81 files
indexing [job 247]: spawning 1 workers to process 1737 / 1737 files
indexing [job 247]: indexed 76 files
indexing [job 248]: spawning 1 workers to process 1737 / 1737 files
indexing [job 248]: indexed 114 files
indexing [job 249]: spawning 1 workers to process 1737 / 1737 files
indexing [job 249]: indexed 117 files
indexing [job 250]: spawning 1 workers to process 1737 / 1737 files
indexing [job 250]: indexed 113 files
indexing [job 251]: spawning 1 workers to process 1737 / 1737 files
indexing [job 251]: indexed 125 files
indexing [job 252]: spawning 1 workers to process 1737 / 1737 files

I’m on build 3156, the latest one at this point in time on macOS 10.12.6.

0 Likes

#7

Get into this issue as well after I put a 3MB .php dictionary file in my project…

0 Likes

#8

Since I passed to 3.2 the indexing steps always on my feet.
Even when it’s completed, Sublime will start to reindex everything when closed and reopened (happened on the same project a couple of times in the last days; but last try didn’t start to reindex).
But note that my projects are reached via NFS, so that might contribute to the problem.

I am also having random crashes, quite often, since the 3.2.
While I can count with two hands how many times SublimeText crashed in the last 5 years, with versions < 3.2. :slightly_frowning_face:
It might be as well related to NFS volumes; something changed there.
Very often I try to unmount those volumes but macOS will give me an error telling me that files are currently used by Sublime; while in the last years there was no problem and Sublime <3.2 was just marking the file as unsaved.

0 Likes