You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rtorrent consumes a lot of memory when downloading or uploading at high speed. The most important problem is that when the speed is lowered, or the rtorrent is directly closed, the occupied memory will not be released.
The system used is debian9 or debian10. The Linux kernel version number is higher than 4.9. Rtorrent runs in the docker environment or runs directly in the current system environment. This problem occurs.
In the case of high memory usage, the load on the CPU is greatly increased.
The same docker image in synology, there is no problem. Currently the core of Synology is 4.4.
It is not certain whether this is caused by libtorrent or by rtorrent.
Is there such a possibility, libtorrent or Rtorrent memory release code, is not compatible with the newer Linux kernel
Does anyone else have the same problem with me?
The text was updated successfully, but these errors were encountered:
badgv
changed the title
Rtorrent takes up a lot of memory, but it doesn't release
Rtorrent memory leak
Jul 29, 2019
Rtorrent consumes a lot of memory when downloading or uploading at high speed. The most important problem is that when the speed is lowered, or the rtorrent is directly closed, the occupied memory will not be released.
The system used is debian9 or debian10. The Linux kernel version number is higher than 4.9. Rtorrent runs in the docker environment or runs directly in the current system environment. This problem occurs.
In the case of high memory usage, the load on the CPU is greatly increased.
The same docker image in synology, there is no problem. Currently the core of Synology is 4.4.
It is not certain whether this is caused by libtorrent or by rtorrent.
Is there such a possibility, libtorrent or Rtorrent memory release code, is not compatible with the newer Linux kernel
Does anyone else have the same problem with me?
The text was updated successfully, but these errors were encountered: