Brackets on mac - using 99% CPU and sluggish

[elliotthill]

Macbook pro retina with Yosemite.

Perhaps this has always been an issue but I've been noticing recently that the editor is very slow to respond, perhaps a few 100ms to register a keystroke. So much so that you can type a sentence, finish and watch the editor catch up.

I am running with no extensions and all JS default extensions deleted. Project size/number of files seems to make no difference.

It also is stuck at ~99% CPU permanently.

[JeffryBooher]

This is strange. The helper APP used to be unresponsive (a known issue) #5794
@elliotthill do you know if this happened with older versions of Brackets on Yosemite?

https://github.com/adobe/brackets/releases/download/release-0.42/Brackets.Release.0.42.dmg (if you want to try Release 0.42)

You'll want to reset your cache and preferences when installing it: https://github.com/adobe/brackets/wiki/Cache-Folder

[elliotthill]

That seems to have fixed the CPU problem, its now sitting at ~1% and peaking at ~30% , its a little more responsive, but keypresses are still a little delayed compared to any IDE/editor i've used.

[JeffryBooher]

@elliotthill thanks for the update. Sounds like the helper app behaves differently on Yosemite that it did on Mavericks.

[JeffryBooher]

Marking this as performance/mac only for now

[peterflynn]

@elliotthill When you say "That seems to have fixed the CPU problem," did you mean clearing preferences, or downgrading to the version 0.42 that Jeff linked to above? If you just did both of those things, can you try moving back to version 1.0 and see if the problem still happens then?

Also, does this happen for all projects, or just some? For example, does it happen if you do this:

1. Launch Brackets
2. Open the 'Getting Started' project that comes with Brackets (it's probably still listed in the 'recent projects' dropdown in the sidebar; if not, you can use File > Open Folder to browse to it).
3. Quit and re-launch Brackets (so only project it has opened since launching is Getting Started)

Do you still see high CPU usage in that case? If not, try to figure out which projects it happens for. If you make a copy of one of your projects and start deleting files from it (restarting Brackets in between, as above), does the problem eventually go away? Which files did you delete right before the problem stopped?

Also, does the problem still happen if you set the "codehint.JSHints" preference to false?

[peterflynn]

Adding 'needs review' label since we need more info before tagging with a feature area

[dangoor]

@elliotthill We can't really proceed without more info, so I'll go ahead and close this. Please feel free to reopen if you have additional information.

[proto-typical]

There is definitely a lag problem, and I have pinpointed that it's directly related to the size of the file you are editing and codehint.JSHints flag set to true. If I start a new file or open one with just 10 lines, there is no lag whatsoever. But working with a file of 2500 lines, it's a horrific lag.

Obviously a workaround is breaking my project down into smaller files, however I think many users would choose to just use a editor that doesn't lag on a 102k text based file.

Let me know if you need more information, I am experiencing this on a Macbook Pro with OSX 10.11.4 (El Capitan) 16GB i5 non-retina SSD and version 1.6 of Brackets, no extensions running.

I posted this on bug #9486 because this is imo the same issue. I also have the CPU usage through the roof when typing in brackets with codehints.JSHints flag set to true.