On Mon, Jul 08, 2024 at 10:48:37AM GMT, Josh Grosse wrote:
> Ping.  This is a bugfix release. Tested on amd64.  -daemon still
> has a non-zero rtable issue reported with 4.0.5.

So, given I was a victim of the rtable issue, I took another attempt at
it.

Josh, do you see the issue if you run transmission-daemon with
"port-forwarding-enabled" set to false? Can be achieve running it -M,
which will also write it to the config. In my setup, it gets stuck when
port forwarding is enabled and it runs in an rtable other than 0. I've
been running with it disable for 2 days without issues is rtable 2.

btw, decided to attempt that after rereading your debug attempts in
Reddit. I believe that you keep looking at the loop in curlThreadFunc
because that's the way that thread works, while taking a look at another
thread showed it was attempting a read that came from natpmp.

iirc, I started experiencing it around mid-May, while the reddit post is
from mid-April. transmission-daemon runs in a machine that runs -current
and is updated on a weekly basis.

	Lucas