Node.js memory leak

[afshinm]

When I try to seed two or three files, more than 30 processes created and the server just stop working.

Here is a screenshot of my server and processes:

Also I got max EventListener error.

[feross]

Those are almost certainly threads, not processes. WebTorrent doesn't ever spawn processes but node.js will spawn new threads for IO tasks.

The problem where everything stops working is the real problem here. How large are the torrents you're seeding? How many are you seeding?

[feross]

Pro-tip: You can configure htop to show only processes, instead of the default of threads.

[afshinm]

Hey @feross

I'm seeding 4 html files, less than 1kb. I figured out that when I start seeding even a 1kb file, nodejs creates about 20 threads. I don't know which module is creating this threads btw.

[rom1504]

Why is it a problem that node create these threads ?

[afshinm]

@rom1504 after seeding 3 html files, you will have more than 100 threads and no memory left.

[rom1504]

How are you seeding these files ? I don't think starting several webtorrent instances is an efficient way to do it.
Are you using webtorrent or webtorrent-hybrid ? There are some performance problems with webtorrent-hybrid currently.

[afshinm]

@rom1504 I'm using webtorrent-hybrid. I don't create several WebTorrent instances but I call add function three times to seed three different files (which makes sense I think)

[feross]

Threads don't necessarily take a notable amount memory.

webtorrent-hybrid has memory issues because of the wrtc module. We should investigate using Electron instead of wrtc. Looking for a volunteer to work on this! webtorrent/webtorrent-hybrid#5

[feross]

Closing because the original issue was invalid (node.js creates lots of threads - not a WebTorrent issue).

webtorrent-hybrid does have memory issues due to wrtc, issue here: webtorrent/webtorrent-hybrid#5