Broken Pipes in application standard output, on some operating systems

[Baaleos]

Summary of the bug:
When piping to the standard output - the content of the output has the ability to interrupt the application itself. I first noticed this when I saw the ffmpeg process never closing.
Then I decided to execute the command line myself- and observed the issue in action.
When the below is executed - the console window will spam with binary data - but then the process will halt and will ask the user:

Enter command: <target> <time> <command>[ <argument>]

I am unsure why the process is prompting with the above - but it is not due to any input from the user.
The strange thing however is that on Windows 10 - this issue is not present.
On Windows Server 2012 R2 - it is
On Ubuntu 18 - it is as well.
How to reproduce:

   -hide_banner -loglevel error -i \"{path}\" -ac 2 -f s16le -ar 48000 pipe:1

I will attempt to attach the mp3 that I was replicating this issue with - so you can reproduce it on your end.

[Baaleos]

Unfortunately the audio file I have is 7mb in size - too big for the ticket.

[Carl Eugen Hoyos]

Please reopen this ticket if you:
Can test current FFmpeg git head.
Remove hide_banner and an error level below default from your command line
Provide the command line you tested together with the complete, uncut console output
If you can upload the input file to a file share of your choice