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

[Dev Perf] CPU usage 95% caused by nano #1325

Closed
mintuz opened this issue May 18, 2015 · 6 comments
Closed

[Dev Perf] CPU usage 95% caused by nano #1325

mintuz opened this issue May 18, 2015 · 6 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@mintuz
Copy link

mintuz commented May 18, 2015

Hello, found a bug in which if you close Xcode, turn off the simulator and shut down the packager, the CPU still sits round 95% and is caused by a nano process hanging around.

@onlymejosh
Copy link

I've been having the same issue. Took me a while to work out what was causing my brand new laptop to run like the old one!

@ide
Copy link
Contributor

ide commented May 29, 2015

@mintuz do you mean nano as in the editor? not sure where this is coming from. The only mention of nano is unrelated.

ide:react-native·master$ grep -r nano .
./node_modules/module-deps/node_modules/JSONStream/test/fixtures/all_npm.json:{"id":"nano","key":"nano","value":{"rev":"105-50efc49a8f6424706af554872002c014"}},
./node_modules/module-deps/node_modules/JSONStream/test/fixtures/all_npm.json:{"id":"nanostate","key":"nanostate","value":{"rev":"9-1664d985e8cdbf16e150ba6ba4d79ae5"}},

@brentvatne brentvatne changed the title bug - CPU usage 95% caused by nano [Dev Perf] CPU usage 95% caused by nano May 29, 2015
@brentvatne
Copy link
Collaborator

Are you still having this issue @mintuz @onlymejosh? Is your shell $EDITOR or $REACT_EDITOR set to nano by any chance?

@mintuz
Copy link
Author

mintuz commented Jun 1, 2015

I do have nano set to my Shell Editor. and it only spikes at 95% CPU when I use React Native on the simulator.

@browniefed
Copy link
Contributor

@brentvatne if it only happens on a simulator is this still an issue worth keeping open?

@ide
Copy link
Contributor

ide commented Sep 13, 2015

Will be addressed by #1957

@javache javache closed this as completed Oct 17, 2015
@facebook facebook locked as resolved and limited conversation to collaborators Jul 22, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 22, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

7 participants