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

Webseeds stuck sometime #963

Closed
nghiemvien opened this issue Oct 29, 2016 · 12 comments
Closed

Webseeds stuck sometime #963

nghiemvien opened this issue Oct 29, 2016 · 12 comments

Comments

@nghiemvien
Copy link

@nghiemvien nghiemvien commented Oct 29, 2016

I created a torrent file with url video in it. Normally when I test with 1 pc, it's work just fine , you can check it here http://webtorrent.bna.vn
When another PC join to watch video, something weird happen, sometime video on PC 1 stop, sometime PC2, and sometime both stop.
Browser doesn't get video from webserver anymore

video : https://www.youtube.com/watch?v=7bUCdWGZRhc&feature=youtu.be

  • WebTorrent version: latest version
  • Browser name/version: latest Chrome
@DiegoRBaquero

This comment has been minimized.

Copy link
Member

@DiegoRBaquero DiegoRBaquero commented Oct 29, 2016

Could you provide debugging logs?

It might be the error where the webseed 'peer' 'chokes' and gets removed

You can activate debugging logs with localStorage.debug = '*'

@nghiemvien

This comment has been minimized.

Copy link
Author

@nghiemvien nghiemvien commented Oct 30, 2016

Here is log from PC1 and PC2. Both got stuck at 12.9%

webtorrent.bna.vn-pc1-1477823017399.txt
webtorrent.bna.vn-pc2-1477823040836.txt

@nghiemvien

This comment has been minimized.

Copy link
Author

@nghiemvien nghiemvien commented Oct 30, 2016

This is log from PC1 after I close browser on PC2. I see :
bittorrent-tracker:websocket-tracker tracker timeout: destroying peer +0ms
webtorrent.min.js:4 simple-peer [0f187ea] destroy (error: null) +0ms

webtorrent.bna.vn-pc1.2-1477823596482.txt

@gpetrov

This comment has been minimized.

Copy link
Contributor

@gpetrov gpetrov commented Nov 4, 2016

Got the same problem when downloading through the webseed it goes only for 17-33% and then it get stuck. Complete event never happens. @feross could you check please?

In my situation the tracker is not always available or it couldn't connect with websockets - but it seems to me that then the webseed should be fully used...

@xuset

This comment has been minimized.

Copy link

@xuset xuset commented Nov 5, 2016

Looking at the logs that were posted. The interesting parts are line 2615 in the pc1 log and line 308 in pc2 log. Those lines correspond to the last piece request to the webseed. Immediately following, pc1 and pc2 form a webrtc connection to each other then both destroy the webseed peer. I'm not sure why the webseed peer is being destroyed in this case, but it may have something to do with pc1 and pc2 connecting since everything was fine before.

@gpetrov

This comment has been minimized.

Copy link
Contributor

@gpetrov gpetrov commented Nov 6, 2016

@DiegoRBaquero yes we got a regularly a "uninterested" following by "choke" in our sample at piece 56 out of 160 and the webseed download hangs...

Is it supposed to recover after choke? Now it just hangs forever...

@gpetrov

This comment has been minimized.

Copy link
Contributor

@gpetrov gpetrov commented Nov 6, 2016

actually it turns our that web seeds shouldn't choke, so addressed the above with #972

@nghiemvien

This comment has been minimized.

Copy link
Author

@nghiemvien nghiemvien commented Nov 12, 2016

So, anyone can fix this bug ?

@rayvahey

This comment has been minimized.

Copy link
Contributor

@rayvahey rayvahey commented Jan 10, 2017

I just found I had this problem too, it seems to lose the webseed object.
In the meantime if you are using a webseed as a fallback like I am, a quick dirty workaround is to check if the torrent.numPeers is zero. Then torrent.addWebSeed(url)
(in the onProgress function)

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Jan 18, 2017

Sorry for the delay on this. This was fixed in #972. Just published a fix as version 0.98.1.

@feross feross closed this Jan 18, 2017
@rayvahey

This comment has been minimized.

Copy link
Contributor

@rayvahey rayvahey commented Jan 18, 2017

Thanks Feross, the fix is working very well.

@bertofer

This comment has been minimized.

Copy link

@bertofer bertofer commented Oct 11, 2017

Hi, I am still having this problem when I put my code online. I made screenshot of the logs

screen shot 2017-10-11 at 18 28 49

This is not happening when testing locally, but occurs when putting everything in the cloud behind an nginx. Trying to figure out if the nginx is doing something wrong. It's still a weird behaviour, as most of the parts seem to download fine, even in large files, it downloads 99% and then gets stuck. With very small files, it get's stuck when there are a couple of pieces missing. Sometimes it gets the whole file (when small). I am not sure what might be happening.

I am using webtorrent 0.98.19 in Chrome, Mac OS X .

Any help? Thanks

@lock lock bot locked as resolved and limited conversation to collaborators May 9, 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
7 participants
You can’t perform that action at this time.