Removing a torrent doesn't release memory in the browser

[skzap]

What version of WebTorrent?
0098

What browser and version?
Chromium 59

What did you expect to happen?
Ability to seed a 500 MB file, remove it, seed another 500MB file, remove it, seed another 500MB file, etc... without the total memory usage growing
What actually happened?
Removing a torrent doesn't release the memory, therefore after a finite amount of steps, the maximum tab memory usage gets reached.

You can open the chrome task manager to check memory usage.(shift + escape)
You can try through https://btorrent.xyz/ where the same behavior happens.

[DedSec002]

This issue is not just with seeding the file but also been a same problem when other common operations done on chrome... You can use plugins to limit the usage on each request you make

[feross]

@skzap Can you share the code you're using that causes this issue?

@DiegoRBaquero Is there any chance that this could be a BTorrent.xyz bug? I'm pretty sure that we don't have any memory leaks like this in WebTorrent anymore.

Specifically, you can add, remove, add, remove many dozens of time in WebTorrent Desktop without memory usage growing, so I don't think the core library could have this issue.

[DiegoRBaquero]

Could be, I'd need to check. @skzap does it happen only in btorrent or is it a general thing?

[no-response]

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 leave a comment or open a new issue if you have the additional information we need so investigate further.