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

Torrent stalled when added > removed > added again #1180

Closed
pldubouilh opened this issue Aug 26, 2017 · 2 comments
Closed

Torrent stalled when added > removed > added again #1180

pldubouilh opened this issue Aug 26, 2017 · 2 comments
Labels

Comments

@pldubouilh
Copy link
Contributor

pldubouilh commented Aug 26, 2017

Webtorrent fails at starting torrents that were previously added and then removed.

I observe that behaviour both in the desktop app and the web-ui for webtorrent I'm writing (here), hence me writing here directly in webtorrent/webtorrent.

What version of WebTorrent?
0.98.19

What operating system and Node.js version?
Archlinux latest kernel, node v8.1.3

What did you expect to happen?
Torrents to start.

What actually happened?

  • Add torrent with magnet link on webtorrent-desktop
  • Wait for it to download (download kicks off instantly on very active torrents)
  • Remove torrent (no matter if it's data or from list)
  • Add magnet link again

... and that's where it's stuck, at Loading torrent.... After leaving it for ~15 minutes it's starting and switching between halted and very low speed (100s of KB/s where the normal speed is close to 10MB/s)

I noticed pausing and restarting sometimes makes it restart at normal speed on webtorrent-desktop.
On the web-ui, the only reliable way I could find was to destroy the client, and restart all the torrents, but that seems a bit drastic !

Thanks !

@Fabiencdp
Copy link

I noticed the same issue when using infohash,
client.add(infoHash)
But it work as excepted when using magnet link or http link.
When using infoHash, then deleting torrent, then reusing the same infoHash, the "on('metadata')" event is not triggered.

@pldubouilh, Did you find a better solution ?

@stale
Copy link

stale bot commented Aug 2, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Aug 2, 2018
@stale stale bot closed this as completed Aug 9, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Nov 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants