-
Notifications
You must be signed in to change notification settings - Fork 96
CPU, RAM drain #111
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
Comments
Thanks for reporting @marcosfede, any ideas what can cause this? |
Not really, I've tried disabling all custom features on the .env file but the problem still persists. Tried on 4 different machines and I seem to have between 3-4 node proceses taking over the cpu in all of them. Let me know if theres anything I should try. Thanks |
Try to update latest react-scripts, i solved this by creating fresh fork of cra and adding just sass which works just Fine. |
i`m facing same issue. |
Having the same issue. |
On my installation those issues were due to webpack-dashboard which was not disabled even if I thought I had done so. See #114 |
Disabling REACT_APP_WEBPACK_DASHBOARD did the trick for me. (I event using it. Maybe, if it was connect it wouldn't cause this. I don't know :/) |
same issue as #110, reopening here since the original author closed that one.
I'm having several node proceses spawned, taking almost 90% of CPU Power and 500Mb of ram each. Hot reloading is also impacted, taking between 5 to 10 seconds to reload after a changed is saved.
OS: Tested on both Linux and Mac
custom-react-scripts version : 0.2.0
react version: 16
The text was updated successfully, but these errors were encountered: