-
Notifications
You must be signed in to change notification settings - Fork 113
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
Wont download but started #169
Comments
I’m having exactly the same issue. I’ve also noticed that the Chrome magnet extension is greyed out and not working. FWIW this only seems to have happened since the ChomeOS ux update. Edit: I’m connecting via broadband not phone. |
You are all on the ChromeOS dev channel? |
I am yes. |
I followed a link from an email i received.
…On Fri, Jul 6, 2018 at 8:32 AM, Adrock45 ***@***.***> wrote:
I am yes.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#169 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AkrNPbFAc__zllP1IZyG6aOzyb5gzB9Sks5uD60ggaJpZM4VBPDc>
.
|
Yes I am using the ChromeOS dev channel Version 69.0.3473.0 (Official Build) dev (64-bit) |
Was there an update/resolution for this? More than happy to do a screen recording if that will help? |
Thanks. I have a device on dev channel now that I can test with. If I can't
reproduce it I'll let you know.
…On Tue, Jul 17, 2018 at 11:36 AM oichapman ***@***.***> wrote:
Was there an update/resolution for this? More than happy to do a screen
recording if that will help?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#169 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJqkDZdnqlefMlj3XOAhTk2jctFqJUSks5uHi68gaJpZM4VBPDc>
.
|
I am able to reproduce now. It seems chrome.sockets.udp.bind is not working after a certain point. After a full system reboot it works. I am not cleanly closing UDP sockets and they don't seem to get cleaned out with a simple chrome.runtime.reload of the app. Check if a full system reboot fixes it. Actually it seems you can do a full logout and login and that will let at least one download work. |
Rebooting or logging on and off hasn’t helped. |
Same issue and reboot doesn't seem to solve it. I'm also in the dev channel. |
I take it back - a reboot does get it going for a while, but after a while it slows down, and only a single torrent will work. When can we expect this to get fixed? |
Sooooo I recently powerwashed my Chromebook and JS torrent works like a charm. Anybody else having issues give that a try. Very happy now. |
I also switched to the stable channel and powerwashed. Works great. |
I found the culprit and filed a bug. |
i have torrents in jstorrent but they are in start and will not go any further. i have the pd version.. im new to chromebook so not really sure whar i am doing..im used to windows downloading very easy to do that...please anyhelp would be appreciated |
Sorry this is probably an easy fix but i can't get it going. Under trackers tab i get timeout errors, just like it says to look for under the help button on the app. Not really sure what to do after that. What's weird it worked fine first time i tried. I bought the app and can't get any download to start after that. I am doing the same thing, which is connecting via a hotspot from my iphone in India. I've tried using a VPN but doesn't work either.
The text was updated successfully, but these errors were encountered: