monotorrent
monotorrent copied to clipboard
looks like monotorrent got memory leak in tracker
it's related to SemaphoreSlimExtensions, after i comment out using (await AnnounceLimiter.EnterAsync ()) everything back to normal
Can you share a minimal repro please?
This should be fixed now. This issue would manifest when there were over 10 tracker tiers in a torrent, and the trackers within that tier frequently timed out or were unresponsive.
The fastpath which discarded excessive announce attempts occurred after rate-limiting was applied, but announce attempts should have been discarded before rate-limiting was applied. That meant a significant queue of attempts could build up when there were dozens/hundreds of tracker tiers, though the majority of those queued attempts would be a no-op in the end.