Process hang with GnuTLS on Linux/ARM64 about fluentftp HOT 9 CLOSED

Thanks for supplying this. I see in the code where this is happening. I'll see what I can to to mitigate this.

from fluentftp.

It turns out that to fully understand what is happening here, I must try to reproduce this or I could make a special branch of FluentFTP.GnuTLS for you, that you could use to produce such a log again with even more detail (sorry!). Do you think you can handle that?

One note: FluentFTP.GnuTLS runs sync and does not honor any cancellation token. So that is no wonder that it will loop and loop... but I would like to find out where and perhaps be able to prevent it.

from fluentftp.

Of course, let me know when you made the branch!
With the even more detail, you mean a higher LogLevel?

from fluentftp.

Same log level but some new diagnostic messages (temporary) in places where I need to see that is happening. Later today...

from fluentftp.

So, this branch: https://github.com/FanDjango/FluentFTP.GnuTLS/tree/TestLoop
Use that instead of the NuGet.
There will be huge amounts of log.
Do a find on "STOR rock.xz" and delete all before that.
Then page forward until you can see the looping write with return -1, take many pages of that and put it in pastebin.
:-)
To reduce the log you could also try:

						LogLevel = 1,
						LogMessages = GnuMessage.Read | GnuMessage.Write,

from fluentftp.

Sorry for the late response, here are the logs:

https://pastebin.com/X53L26JH

Also, no high CPU usage!

from fluentftp.

Thanks, very helpful. I already fixed a few things, and will make a few more changes thanks to this log you sent.

Looks good now, right?

from fluentftp.

I have merged the changes to FluentFTP.GnuTLS (current master) and will later cut a new Nuget release.

from fluentftp.

Yes looks great! I checked out the master branch as well just to be sure.
Little heads up, the verbose logs I think are hardcoded into the GnuTLS, because it shows up even with logging turned off.

from fluentftp.