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

Webtorrent doesn't call callback of add when files are too big #944

Closed
antoniomuso opened this issue Oct 10, 2016 · 2 comments
Closed

Webtorrent doesn't call callback of add when files are too big #944

antoniomuso opened this issue Oct 10, 2016 · 2 comments

Comments

@antoniomuso
Copy link

@antoniomuso antoniomuso commented Oct 10, 2016

Hi , I have a problem when file is too big.
When i run program in my computer desktop(Windows 10) it works well, but if i run program in RaspBerry PI (Debian "Raspian") it doesn't work if I add big files. it isn't a memory issues.

@antoniomuso antoniomuso changed the title Webtorrent doesn't call callback of add when files is soo big Webtorrent doesn't call callback of add when files is too big Oct 10, 2016
@antoniomuso antoniomuso changed the title Webtorrent doesn't call callback of add when files is too big Webtorrent doesn't call callback of add when files are too big Oct 10, 2016
@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Oct 11, 2016

  • How much memory does your Raspberry Pi have?
  • What version of Raspian are you running?
  • Is Raspian 32 or 64-bit?
  • How large is the torrent that is failing?
  • Can you figure out the size at which WebTorrent starts to fail? For example, does it work for 3GB torrents, but fail for 4GB ones?
  • Can you run your program with the following environment variable DEBUG=*,-bittorrent-dht and post the logs of when it fails?
@no-response no-response bot closed this May 3, 2018
@no-response

This comment has been minimized.

Copy link

@no-response no-response bot commented May 3, 2018

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 1, 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.