ssed: couldn't flush stdout: No error

in windows command prompt
after using ssed and pipe it several times
I always get the message, "ssed: couldn't flush stdout: No error"
ssed is originally linux, after ported to windows, so the error comes out
for example
\n in s/a/\n/g is not well handled, after pipe, that ssed won't quit
and remains until the whole command chain quits
then error occurs