We've noticed that if a client suddenly terminates without cleanly closing the connection to fluentd-forwarder, then the forwarder starts to emit loads of messages like:

... temporary failure: read tcp from 127.0.0.1... An existing connection was forcibly closed by the remote host.

This happens on Windows.

Maybe golang issue #6163 and this fix could be related?

It would be nice if fluentd-forwarder was more resilient to abrupt client terminations.
Is there anything we can do on our side?

Thanks!