Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upWith a large number of torrents (> 500) WebTorrent blocks, making the entire machine unresponsive #625
Labels
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This comment has been minimized.
This comment has been minimized.
|
WebTorrent needs resource management - this is a known issue. |
This comment has been minimized.
This comment has been minimized.
|
this may be related to: In chrome it's fixed, but there is a quota for blobs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Upon re-adding 500 torrents to WebTorrent (on node, under Linux) the machine basically dies by becoming unresponsive and a hard reboot is required to continue operation.
This is the last output to the console I managed to capture:
From what I've read online the problem seems to be with I/O going synchronous when overloaded.
I think the solution might be to set a static, configurable limit on all the I/O done by WebTorrent instances.
Equally, IP connections should have a static, global limit, as in default Ubuntu configuration (without changes to
sysctl) I'm experiencing global connections (unrelated to WebTorrent) being dropped very soon (even with only 100 torrents in the instance).I realize running 500, or even 100 torrents at the same time is not something most people want to do, but there should be some basic safeguards from the app crashing the system.