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

electron-eval error: Electron process exited with code 2 #1075

Closed
chovy opened this issue Mar 9, 2017 · 7 comments
Closed

electron-eval error: Electron process exited with code 2 #1075

chovy opened this issue Mar 9, 2017 · 7 comments

Comments

@chovy
Copy link
Contributor

@chovy chovy commented Mar 9, 2017


UNEXPECTED ERROR: If this is a bug in WebTorrent, report it!
OPEN AN ISSUE: https://github.com/feross/webtorrent/issues

DEBUG INFO: webtorrent-cli 1.9.0, webtorrent 0.98.10, node v7.7.1, linux x64, exit 1
events.js:163
      throw er; // Unhandled 'error' event
      ^

Error: electron-eval error: Electron process exited with code 2
    at ChildProcess.<anonymous> (/home/example/.nvm/versions/node/v7.7.1/lib/node_modules/webtorrent-hybrid/node_modules/electron-eval/lib/index.js:174:22)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:194:7)
    at maybeClose (internal/child_process.js:899:16)
    at Socket.<anonymous> (internal/child_process.js:342:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at Pipe._handle.close [as _onclose] (net.js:504:12)

This happens when I seed more than one file. One usually seems to work ok, but if i have 2-3 it crashes frequently. Probably a memory/resource issues -- its on a $5 vps.

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Mar 9, 2017

If you have to seed many files, I recommend using http web seeds instead of webtorrent-hybrid. They will be much more reliable.

@feross feross closed this Mar 9, 2017
@chovy

This comment has been minimized.

Copy link
Contributor Author

@chovy chovy commented Mar 10, 2017

I am confused. isn't webtorrent a cli torrent client? It can only seed one file at a time?

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Mar 10, 2017

WebTorrent isn't a CLI torrent client. It's a JavaScript torrent client that has many different frontends. It can be used via an official CLI, a desktop app, or a <script> tag in a browser.

The CLI only supports one torrent at a time. Use the desktop app if you want to seed multiple torrents.

@chovy

This comment has been minimized.

Copy link
Contributor Author

@chovy chovy commented Mar 10, 2017

gotcha. i thought cli was a full blown torrent client. i was hoping to replace rtorrent with it. but i guess that isn't possible since you need desktop app to do multi seeds

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Mar 10, 2017

Yes, sorry. If someone else wants to build a full-featured CLI torrent client on top of the webtorrent engine, they should feel free. It's not something I want to do. Since most users want a GUI, I'd rather put my effort there.

@chovy

This comment has been minimized.

Copy link
Contributor Author

@chovy chovy commented Mar 10, 2017

Makes sense. Dont' mean to bombard you with all these questions -- but this project looks very promising and I'm sure others will have same questions, so at least there is a record. A multi-seed cli would be nice since a lot of people are moving to seedboxes out of simplicity and faster speeds.

Don't know how difficult it would be to implement, I'm assuming if it was easy you would have done it already.

@lock

This comment has been minimized.

Copy link

@lock lock bot commented May 3, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.