-
Notifications
You must be signed in to change notification settings - Fork 495
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
Ctrl+C on Ubuntu 14.04 LTS doesn't kill geth, geth takes massive amounts of CPU #81
Comments
I've got this problem too. I'm using Vagrant to set up a VM to run this stuff. See: https://gist.github.com/tom-seddon/407df5a095043a954448 (for OS X - tweak the vb.cpus setting if running on Linux/Windows) You can reproduce it by setting up the above VM then doing something like:
then once it's done the building DAG, and mined a couple of blocks, and decided to stop (since the default is the mine-on-demand mode), press Ctrl+C. Then use The fix I've found seems to be to set When geth does get stuck, you can attach remotely with something like --Tom |
Another option might be to clone https://github.com/jesuscript/vagrant-dapp-env and replace its setup.yml with this very similar one that just specifies versions for a few components: https://gist.github.com/tom-seddon/0dd45250f95121451229 (I decided which versions to use in both these cases by running a VM that does work - vagrant-dapp-env, but built a couple of weeks ago - noting version numbers for geth and solc, and then installing packages on a new VM until I found ones that installed versions of geth and solc that purported to be the same version. Though I note that the geth I get today was supposedly built with go 1.5, whereas the one from 2 weeks ago was built with go 1.4.2.) --Tom |
Interesting thing I also discovered. If you set |
Having the same issue on #123 . Removing the Setting |
this was an issue with geth that has been fixed since then. as for the /tmp/ folder, embark 2.0 no longer uses that folder and shouldn't have the same issue |
@iurimatias I've already made this issue clear via Gitter, but I want to see if there would be other people willing to help tackle this.
This happens after I try to end the session following a
embark blockchain
command. It kills geth in the shell, however, geth is not dead and lives. PIDs show that it takes up to 50% of CPU resources. Prior to this, the automatic miner works just as you would expect. It's kind of an annoyance having to go into the task manager and seek out and kill geth, so any and all help in solving this is greatly appreciated. Much thanks guys.The text was updated successfully, but these errors were encountered: