New release?

[Neustradamus]

Dear rtorrent team, @rakshasa,

It is possible to create a new release build?

The latest is 0.9.8 (2019-07-19):

• https://github.com/rakshasa/rtorrent/releases
• https://github.com/rakshasa/rtorrent/tags

Thanks in advance.

[stickz]

The project is dead, hasn't been updated in a year. It could use a fork for anyone that knows C/C++

How about a fork that is 40% faster, higher performing, more stable/polished and more secure?
https://github.com/stickz/rtorrent

[WagnerGMD]

From another point of view, it's worst for the people which rather a good (official or reliable) release (not my case).
Because the both latest stable rtorrent-v0.9.8 and the stable libtorrent-v0.13.8 were published on the 19 July 2019 (the both are dead since 5 years ago).

Finally there is something : Thank you for the discovery @stickz because I don't know when but one day, i will replace it by an alternative (easy to compile ? Not obvious to choose for example the qbittorent-nox require the libtorrent-rasterbar which have a very long documentation (which could be also too old)).

PS : I will give you one advice, it will better to read (follow) the Changelog of xmlrpc-c (basically replace the super_stable by the branch advanced which is far reliable (around 8 years = only one big trouble).

[davorb]

The project is dead, hasn't been updated in a year. It could use a fork for anyone that knows C/C++

Is it really dead? I see commits from this week on master.

[rakshasa]

I've started working on rtorrent again, so should see some more activity.

[stickz]

@rakshasa I have 3 more very simple pull requests coming to fix some big problems with rTorrent. Afterwards, I would like to kindly request a new release be posted. This will allow Linux operating systems and other platforms to adopt the changes.

1. The first pull request is located here: Fix Link Time Optimizations #1291

2. Is a 1 line fix for a critical memory leak with RPC commands.

3. Is a 10 line fix for session file data corruption due to sudden loss of power.

cc: @anthonyryan1

[rakshasa]

Done, let me know ones it's been tested.

[Neustradamus]

@rakshasa: Nice to see your comeback.

What have you done?

Do not forget to create a new release for rtorrent:

• https://github.com/rakshasa/rtorrent/releases

And libtorrent too:

• New release? libtorrent#234
• Several branches libtorrent#233

I have sent you an e-mail.

[stickz]

@Neustradamus We are testing the master branch for libtorrent and rTorrent currently. rakshasa and I are being sponsored by a third party to improve rTorrent. I will advise rakshasa once these changes are tested, so a release can be posted.

libtorrent

1. Significant performance improvements to improve throughput and reduce CPU usage.
2. A fix for a torrent client crash with the socket address object.
3. Support for 33 gigabit speed throttles on ruTorrent.

rTorrent

1. A fix for a torrent client stack overflow crash with the lockfile buffer.
2. New trackers.delay_scrape command for .rtorrent.rc to avoid crashes with thousands of torrents and allow instant startups.
3. A fix for compiling the software with LTO (Link Time Optimizations) for additional performance.
4. A fix for a critical memory leak with RPC commands which may waste an alarming amount of memory.
5. A fix for critical torrent client breakage if a power outage/failure occurs during a session saving interval.

[rakshasa]

Since there's no complaints thus far, I'll do a release soon.

[Neustradamus]

@stickz, @rakshasa: Thanks for your answers!

@rakshasa: Please look your mailbox, it is important.
Thanks in advance.

[rakshasa]

Release is out.

[Neustradamus]

@rakshasa: Thanks for 0.10.0!

• https://github.com/rakshasa/rtorrent/releases/tag/v0.10.0

Have you received my e-mail?