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

--list option is broken #95

Closed
genseric opened this issue Sep 17, 2014 · 2 comments
Closed

--list option is broken #95

genseric opened this issue Sep 17, 2014 · 2 comments

Comments

@genseric
Copy link

@genseric genseric commented Sep 17, 2014

using the v .7.3 , i am experiencing the problem on a 350+kb torrent file with 250 files of content. the --list does not work

when i run the list i get the error:
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
at Piece.addListener (events.js:160:15)

and it just hangs till i send an interrupt.

@ghost

This comment has been minimized.

Copy link

@ghost ghost commented Sep 20, 2014

have found something here: http://stackoverflow.com/questions/9768444/possible-eventemitter-memory-leak-detected

looks like that the MaxListeners needs to be set manually higher because the error message contains that the MaxListeners need to be increased.

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Oct 9, 2014

Can you send me the torrent file that's causing this issue? My email is feross@feross.org.

@feross feross changed the title error on list command with big files --list option is broken Oct 10, 2014
feross added a commit that referenced this issue Oct 10, 2014
@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Oct 10, 2014

Okay, the issue was that the --list command got broken in the last refactor of the command line app. I just fixed it and published a new version, 0.8.1. You can get it by running npm update webtorrent -g.

@feross feross closed this Oct 10, 2014
@lock lock bot locked as resolved and limited conversation to collaborators May 7, 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.