4 ms·
I've been running the last stable build happily since August. Running this new build causes all four cores in my rmbp to spin up to 99% repeatedly (Activity Mon
by ashes2 12y ago
I've been running the last stable build happily since August. Running this new build causes all four cores in my rmbp to spin up to 99% repeatedly (Activity Monitor says it's Sublime) and the fans to go wild. Is this happening to anyone else? I had to revert to the previous version which fixed it :(
- nxbtch 12y agonope
- bumbu 12y agoSimilarly for me. On every file change ST status bar says - indexing files. And it takes > 10s (I have a lot of files). When it does that - 2 CPU cores are loaded at 99%. Opened the console (@jskinner suggested to enter sublime.log_indexing(True)) and there was a message that index is corrupted and I have to remove it. Index is located in: /Users/bumbu/Library/Application Support/Sublime Text 3/Index Removing all the files from that folder did the trick.
- jskinner 12y agohttp://www.sublimetext.com/forum http://www.sublimetext.com/forum is a better place for this, but as a stopgap you can disable file indexing via the index_files setting. You can also find out more about what indexing is taking place by entering sublime.log_indexing(True) in Sublime Text's console.
- d4n3 12y agoFor me it was trying to index a huge folder containing images, you can use project settings to exclude some folders with the folder_exclude_patterns setting.
- paraboul 12y agoLet it go for 1 hour. It's just indexing your files the first time.
- FooBarWidget 12y agoI ran into this too. It's because of the index that Sublime builds for its Goto Anything feature. If you never use Goto Anything, in your User Settings: "index_files": false