Cœur

I'm exclusively using magnets, and no more issues of any sort since 4a80f800a60a52c00ae014074caadaa282666d81. @arcticfoxwpg @chaseholden kindly try a recent build, thanks.

@arcticfoxwpg which issue number is it? If there are none, you'd need to create an issue for your crash, with a crash log.

I'm afraid I don't know how to help with your magnet issue. Feel free to investigate by looking at the code and your message logs.

Notes: Fixed macOS warnings and deprecations.

OK, but you left my questions unanswered. >How did you build the app? >Can you try to clean your build folder, delete the app and rebuild+reinstall it?

Ah then, Tockman, yours is possibly a duplicate of #3400 I would say. :) But possibly chaseholden issue had the same root cause too. Unfortunately, since it's non trivial to...

Marking as duplicate of #3400, but keeping it open as it has a nice video of the issue, showing a slightly different situation than the previous issue.

In case it's still happening for you, then with current code: https://github.com/transmission/transmission/blob/92b74fee742822841a56b1b7ab835653c91c997c/libtransmission/peer-msgs.cc#L2189 ## First error - what=17 is "error encountered while reading" + "eof file reached" - errno=0 is "Undefined...

Just like with previous log change, we should just put it as `logtrace` instead of `logdbg` when the errno is 2.

But lets recall that those are UTP errors, and that the UTP lib is filled with bugs of the sort: >SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /Users/User/Developer/transmission/third-party/libutp/utp_internal.cpp:2574:77 in /Users/User/Developer/transmission/third-party/libutp/utp_internal.cpp:2574:77: runtime error: store to...