Webtorrent-desktop: Webtorrent for desktop becomes unstable when downloading large files

[Vishnu05]

I'm using Windows 10, web-torrent v.23
This issue I'm facing for a long time when I try to download a large size file. Web torrent becomes unstable and it makes my system to become unstable finally the web torrent crashes

And sometimes it shows 100 to 200mbs for downloading and takes a while to download for 2gigs file

Issues start with if the file size goes beyond 8gigs(approx) web torrent takes to much of ram and my Disk read and write operation becomes 100% and crashes

Node version 14, npm 6.14.0

Need some patch update for this fix.

What version of this package are you using?

What operating system, Node.js, and npm version?

What happened?

What did you expect to happen?

Are you willing to submit a pull request to fix this bug?

[sebastienvercammen]

Hi @Vishnu05, thanks for the bug report.

Could you include some screenshots of Windows' Resource Monitor, with the charts on the Overview tab, while the torrent is downloading and usage is building up to the point of crashing?

[Vishnu05]

Hi @sebastienvercammen
Hope this helps

It takes more than 4gigs of ram, and disk space 100% and I'm not able to use my lap
The only way to use my lap is to kill the resource force stopping the webtorrent to get my lap to the original state

[stale[bot]]

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.

[Vishnu05]

@feross Can you have a look at this!

[feross]

I think this is two issues:

1. This is related to us not having a resource queue https://github.com/webtorrent/webtorrent/issues/1026
2. We use more RAM than we need to for a large files which are downloading quickly because we keep pieces in memory until they're fully downloaded at which point we write them to disk. https://github.com/webtorrent/webtorrent/issues/1973

[feross]

Since there are already issues for these in webtorrent, I'm going to close this issue. Feel free to follow along there.