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 stalls while app window is open #9
Comments
Yes, back when I was developing this I noticed that a substantial amount of processing time goes into UI bookshopkeeping. Perhaps we're updating our model much too often for Angular.js. I don't know, very sorry. Perhaps it would help to limit to fewer peers. |
Saw that you signed up just for this bug report... I've got a ton of stuff on my hands and therefore cannot sink time in this project at the moment. Still, I've started contributing to webtorrent.io which is going to be the next generation of this stuff. It is going to be that much better, but give it time. |
Thanks for letting me know. On 11 January 2015 at 18:21, Astro notifications@github.com wrote:
|
I'm starring webtorrent. Different to this? http://jstorrent.com/ On 14 January 2015 at 00:58, Paul Wright paulwrighthome@gmail.com wrote:
|
Yes, entirely different project. |
Sorry, what I meant was, how are the projects different? On 14 January 2015 at 08:42, Astro notifications@github.com wrote:
|
I'm using Bitford on a Chromebook. I've noticed that the transfer rate dwindles to zero on some torrents. When I close the app window, Bitford keeps running as a background page (in the Chrome Task Manager) using about 500MB RAM and 100% CPU. When I reopen the app window, the torrent has made progress. The transfer rate starts off high, but again dwindles to zero over about 60 sec.
I'm attaching a screenshot showing a pretty long list of peers, but all at zero. The Pieces graph looks a bit odd to me, as they usually go straight from grey to green, only very briefly other colours. The graph you see was stuck like this: no movement.
Sorry if this is vague and non-technical: I'm not a coder. If you need more details please let me know.
The text was updated successfully, but these errors were encountered: