Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node 6 uses full CPU core #6459

Closed
alejandroiglesias opened this issue Apr 29, 2016 · 12 comments
Closed

Node 6 uses full CPU core #6459

alejandroiglesias opened this issue Apr 29, 2016 · 12 comments
Labels
invalid Issues and PRs that are invalid.

Comments

@alejandroiglesias
Copy link

  • Version: 6
  • Platform: OSX 10.11.4
  • Subsystem:

Node process starts using a 100% CPU core after updating from 5.10.1 to version 6. Not sure what other details to give other that I ran npm start on my project which runs the following command: webpack-dev-server --port 4444 --hot --inline --progress --colors. I have the same running at 0.0 CPU usage right now with version 5.10.1.
If you need more information, please let me know.

@addaleax
Copy link
Member

You should probably try asking at https://github.com/webpack/webpack-dev-server rather than here, if that specific application is affected.

@Fishrock123
Copy link
Member

Sounds like a duplicate of #6416

@addaleax
Copy link
Member

@Fishrock123 That sounds very unlikely, among other things because that other issue is actually rather about infinite recursion than about an infinite loop and throws an RangeError almost instantly. Plus, #6416 is ancient and not new in v6.

@mscdex
Copy link
Contributor

mscdex commented Apr 29, 2016

@alejandroiglesias Can you peek into the process to see what it's doing (e.g. using strace or even trying to attach to the node debugger if possible)?

@mscdex mscdex added the v6.x label Apr 29, 2016
@babeal
Copy link

babeal commented Apr 30, 2016

I'm seeing the same thing. Not using dev server but I am using web pack and karma. Any thing that continues execution in a watch mode takes a full core: karma start, web pack -w and web storm's integration with karma. Just wanted to add detail to this issue.

@skyblue
Copy link

skyblue commented May 26, 2016

same issue when use v6 && webpack -w
it look like fs.watch change?

@bnoordhuis
Copy link
Member

Has anyone reported this to webpack yet? We can't do much without a minimal test case. If it requires installing all of webpack, I doubt anyone is going to look at it.

@Florian-R
Copy link

IIRC, both Karma and Webpack use Chokidar under the hood, so this might be paulmillr/chokidar#447

@macrozone
Copy link

We observed the same issue with a meteor-application (not using webpack).

On node4, cpu is low, on node6 always 100% (but in io-wait or similar)

@mulleady1
Copy link

npm rebuild fsevents fixed it for me.

@bnoordhuis
Copy link
Member

I'll go ahead and close this then. It doesn't appear to be an issue with node.js core.

@bnoordhuis bnoordhuis added the invalid Issues and PRs that are invalid. label Oct 29, 2016
@plh97
Copy link

plh97 commented Aug 24, 2019

so, it is caused by webpack-server-dev????

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid Issues and PRs that are invalid.
Projects
None yet
Development

No branches or pull requests