Long running process and high CPU usage

[petecoop]

Over the past few days I've noticed my fans starting to blaze up after a while. It seems to be down to this plugin - here's a couple of instances of long running processes using a lot of CPU taken from ps aux:

USER              PID  %CPU %MEM      VSZ    RSS   TT  STAT STARTED      TIME COMMAND
pete            18985 100.0  0.6  3105256  51124   ??  R     4:21pm  50:43.33 /Applications/Atom.app/Contents/Resources/app/apm/bin/node /Users/pete/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --verbose --extract=auto /var/folders/s4/3c8wrl2x6mv55gj8krrqr1bw0000gn/T/AtomLinter115426-18022-1dyfumisource.js/datatable.js
pete            18706  99.2  0.6  3097064  51152   ??  R     4:19pm  52:56.01 /Applications/Atom.app/Contents/Resources/app/apm/bin/node /Users/pete/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --verbose --extract=auto /var/folders/s4/3c8wrl2x6mv55gj8krrqr1bw0000gn/T/AtomLinter115426-18022-1w2lebjsource.js/datatable.js

The datatable.js file it seemed to be struggling with was using ES6 syntax, was also from an instance of atom that I had closed.

[dustinmoorenet]

I am also experiencing this issue as well. I have noticed it on two separate machines. One with ES6 syntax and one without. This has been happening since at least Thursday (5/21). If I kill the node processes and disable linter-jshint in Atom, all is good. The issue happens within an hour of coding in Atom.

dustin          64597 100.5  0.6  3060200  54360   ??  R    12:07PM   7:51.77 /Applications/Atom.app/Contents/Resources/app/apm/bin/node /Users/dustin/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --verbose --extract=auto -c /Users/dustin/dev/pappy/.jshintrc /var/folders/s7/4cpvsng5761dxc_cr549z9c80000gn/T/AtomLinter115426-64317-13g085jsource.js/EndiciaStatus.js
dustin          64596 100.5  0.6  3060200  51280   ??  R    12:07PM   7:54.66 /Applications/Atom.app/Contents/Resources/app/apm/bin/node /Users/dustin/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --verbose --extract=auto -c /Users/dustin/dev/pappy/.jshintrc /var/folders/s7/4cpvsng5761dxc_cr549z9c80000gn/T/AtomLinter115426-64317-13848z3source.js/EndiciaStatus.js

[jeffcharles]

Also experiencing this issue.

After exiting atom, I see this:

14325 ??        33:29.15 /Applications/Atom.app/Contents/Resources/app/apm/bin/node /Users/jcharles/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --verbose --extract=auto -c /Users/jcharles/projects/cabinet/.jshintrc --exclude-path /Users/jcharles/projects/cabinet/.jshintignore /var/folders/zr/y17gd1hn2bs4nrw520y9j9cdz3r4xx/T/AtomLinter115426-1587-t4zno5source.js/logging.js
14329 ??        33:28.17 /Applications/Atom.app/Contents/Resources/app/apm/bin/node /Users/jcharles/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --verbose --extract=auto -c /Users/jcharles/projects/cabinet/.jshintrc --exclude-path /Users/jcharles/projects/cabinet/.jshintignore /var/folders/zr/y17gd1hn2bs4nrw520y9j9cdz3r4xx/T/AtomLinter115426-1587-1kxy8z7source.js/logging.js
14331 ??        33:23.46 /Applications/Atom.app/Contents/Resources/app/apm/bin/node /Users/jcharles/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --verbose --extract=auto -c /Users/jcharles/projects/cabinet/.jshintrc --exclude-path /Users/jcharles/projects/cabinet/.jshintignore /var/folders/zr/y17gd1hn2bs4nrw520y9j9cdz3r4xx/T/AtomLinter115426-1587-1vzn6gsource.js/logging.js
14333 ??        33:21.40 /Applications/Atom.app/Contents/Resources/app/apm/bin/node /Users/jcharles/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --verbose --extract=auto -c /Users/jcharles/projects/cabinet/.jshintrc --exclude-path /Users/jcharles/projects/cabinet/.jshintignore /var/folders/zr/y17gd1hn2bs4nrw520y9j9cdz3r4xx/T/AtomLinter115426-1587-1chkki5source.js/logging.js
14335 ??        33:18.99 /Applications/Atom.app/Contents/Resources/app/apm/bin/node /Users/jcharles/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --verbose --extract=auto -c /Users/jcharles/projects/cabinet/.jshintrc --exclude-path /Users/jcharles/projects/cabinet/.jshintignore /var/folders/zr/y17gd1hn2bs4nrw520y9j9cdz3r4xx/T/AtomLinter115426-1587-fv1a2usource.js/logging.js
14339 ??        33:14.16 /Applications/Atom.app/Contents/Resources/app/apm/bin/node /Users/jcharles/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --verbose --extract=auto -c /Users/jcharles/projects/cabinet/.jshintrc --exclude-path /Users/jcharles/projects/cabinet/.jshintignore /var/folders/zr/y17gd1hn2bs4nrw520y9j9cdz3r4xx/T/AtomLinter115426-1587-7of0uvsource.js/logging.js
14341 ??        33:11.53 /Applications/Atom.app/Contents/Resources/app/apm/bin/node /Users/jcharles/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --verbose --extract=auto -c /Users/jcharles/projects/cabinet/.jshintrc --exclude-path /Users/jcharles/projects/cabinet/.jshintignore /var/folders/zr/y17gd1hn2bs4nrw520y9j9cdz3r4xx/T/AtomLinter115426-1587-ca9lrmsource.js/logging.js
14343 ??        33:07.54 /Applications/Atom.app/Contents/Resources/app/apm/bin/node /Users/jcharles/.atom/packages/linter-jshint/node_modules/jshint/bin/jshint --verbose --extract=auto -c /Users/jcharles/projects/cabinet/.jshintrc --exclude-path /Users/jcharles/projects/cabinet/.jshintignore /var/folders/zr/y17gd1hn2bs4nrw520y9j9cdz3r4xx/T/AtomLinter115426-1587-1ra8m7hsource.js/logging.js

Not sure why these are all still running even after exiting Atom.

[clementai]

I think I have the same issue : atom/atom#6970

[dustinmoorenet]

It is my impression that a jshint process is run for each file that needs hinting and then exits, and our problem is that the process gets stuck. The process shouldn't be running for any amount of time. I am keeping my Mac cool by running pkill -9 -f jshint every time the fan kicks on. You can double check what you are about to kill by running pgrep -f jshint

[davewasmer]

I've noticed the same. Downgrading to 1.4.0 (apm install linter-jshint@1.4.0) seems to resolve the issue (for now at least).

Looking at the commit history, it looks like it would have to be one of these two one-line changes that introduced the problem:

• 20bc680
• 7ee35d8

Unfortunately, I'm not familiar enough with Atom to guess which. Perhaps @kevinsawicki could weigh in.

Update: Downgrading doesn't seem to work after all.

[textedit]

Same issue here with 0.1.5. Works fine with 0.1.4.

[atom-project]

+1

[steelbrain]

Gonna fix this in the transition of making this linter plus API compatible.

[antonosmond]

I've had the same problem - to reproduce:

1. open a new atom file
2. ensure the source type is JavaScript
3. Type function

It's at the point you type function that a node process gets launched.
If you do a killall node and make sure you have no node processes running, once you've typed function, do a pgrep node and it will have started a node process.

For now, if you want to avoid this undocumented feature, try writing your JavaScript without functions! :)

Hope this helps.

[petecoop]

@antonosmond brilliant fix 👍